Quetz-frontend
The Open-Source Server for Conda Packages
| part of mamba-org | ||
|---|---|---|
| Package Manager mamba | Package Server quetz | Package Builder boa |
Development
First of all, clone quetz and quetz-frontend, create a conda environment using the environment.yml in quetz, run quetz and modify its config file.
# Create an environment
mamba env create -f quetz/environment.yml
mamba activate quetz
mamba install -c conda-forge nodejs=16 yarn=1.22
Install Quetz in dev mode
cd quetz
pip install -e .
# Run quetz
quetz run test_quetz --delete --copy-conf ./dev_config.toml --dev --reload
Modify the quetz/test_quetz/config.toml file to add the client_id, client_secret, github username and the front-end paths.
[github]
# Register the app here: https://github.com/settings/applications/new
client_id = "id"
client_secret = "secret"
[users]
admins = ["github:username"]
Install Quetz-Frontend in dev mode
# build the app
pip install -e .
# Create a link to the quetz folder
quetz-frontend link-frontend --development
Useful commands
# Start an already configured quetz deployment in dev mode:
quetz start test_quetz --reload
# Build the Quetz-frontend
yarn run build
# Build the Quetz-Frontend in watch mode
yarn run watch
Disabling extensions
"quetz": {
"extension": true,
"outputDir": "quetz_light_theme/quetzextension",
"themePath": "style/index.css",
"disabledExtensions": ["quetz-theme"]
},
Command line tool
Quetz fronted also comes with a cli to manage extensions
Usage: quetz-frontend [OPTIONS] COMMAND [ARGS]...
Options:
--install-completion Install completion for the current shell.
--show-completion Show completion for the current shell, to copy it or
customize the installation.
--help Show this message and exit.
Commands:
build Build an extension
clean Clean the extensions directory
clean-frontend Clean the Quetz-Frontend
develop Build and install an extension in dev mode
install Build and install an extension
link-frontend Intall the Quetz-Frontend
list List of extensions
paths
watch Watch an extension
Metadata
Release files for quetz-frontend 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| quetz-frontend-0.4.1.tar.gz | 4.1 MB | Without provenance | Details for quetz-frontend-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quetz_frontend-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for quetz_frontend-0.4.1-py3-none-any.whl |
Total release size: 10.4 MB
Release files / quetz-frontend-0.4.1.tar.gz
| Download URL | quetz-frontend-0.4.1.tar.gz |
|---|---|
| Size | 4.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e23fe342fec6c300ed2684eaebde665ff9f916ce4b0a6fbfabddd18d84b6d031
|
|
BLAKE2b-256 checksum How to use checksums |
315ab79a46131ec00abfe82f23f0097dbf4e2b124869ce0fcba6e0bb90d337dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / quetz_frontend-0.4.1-py3-none-any.whl
| Download URL | quetz_frontend-0.4.1-py3-none-any.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63f830d5d244f1a3821731fb4743425ae0cc22e3e8b332e291277081e8a98b5e
|
|
BLAKE2b-256 checksum How to use checksums |
96aba0fe9bbd28c685795eb8dfbabe81efb370ebd94c2fb581e0b8a630e61a97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for quetz-frontend 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.