https://github.com/conda/schemas

Conda file formats and schemas
https://github.com/conda/schemas

Last synced: 6 months ago
JSON representation

Conda file formats and schemas

• Host: GitHub
• URL: https://github.com/conda/schemas
• Owner: conda
• Created: 2020-03-25T22:03:04.000Z (almost 6 years ago)
• Default Branch: main
• Last Pushed: 2025-07-14T16:32:44.000Z (6 months ago)
• Last Synced: 2025-07-14T21:17:29.036Z (6 months ago)
• Language: CSS
• Homepage: https://schemas.conda.org/
• Size: 155 KB
• Stars: 11
• Watchers: 11
• Forks: 15
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
# Conda Schemas

> **Warning**

> The schemas within this repository are considered works in

> progress/drafts.  Their contents may not fully reflect the current state of

> `conda` and associated tools.

Schemas for the conda ecosystem.

This repository is published to https://schemas.conda.org.

## Contribution workflow

The website logic is available at `site/`.

1. Create a new environment with `python >=3.12` and the requirements in `site/requirements.txt`. For example: `conda create -n schemas "python>=3.12" --file site/requirements.txt`.

2. With the activated environment, regenerate the site with `python site/publish.py`.

3. The generated contents are available at `_build/`. Serve it in your browser with `python -m http.server -d -build/`.

Details about each `site/` item:

- `index.j2.html`: HTML document templated with Jinja.

- `config.toml`: The variables used to render the HTML template.

- `_static/`: Anything in this directory is copied as is to `_build/`.

- `publish.py`: Python script to load the HTML template and render it with the contents in `config.toml`. It also handles `_static/` contents.

- `requirements.txt`: The dependencies needed by `publish.py`.

## Conventions for schema locations

- Ecosystem-wide schemas go in the "General" section. Example: `repodata.json`.

- Application-specific schemas go under a dedicated section. Example: `menuinst` schemas.