scheming.dataset_schemas in .env on Docker usage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 182
- PR merge metrics
- No merged PRs in 30d
Description
The extension is correctly installed on my Ckan container; I was also able to place my dataset.yaml file in a directory within the Ckan container (and it hasn't been overwritten).
I added this line to the .env file to point the schema to the dataset.yaml file in the container
SCHEMING__DATASET_SCHEMAS = /etc/ckan/dataset.yaml
When i use this url : https://localhost :5000/api/3/action/scheming_dataset_schema_list
-> Success :true, result : []
So dataset_schema is not founded
I also tried that -> CKAN__SCHEMING__DATASET_SCHEMAS = /etc/ckan/dataset.yaml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking how the Docker container loads environment variables and how the scheming_dataset_schema_list endpoint resolves dataset schemas. Verify the dataset.yaml path inside the container and compare the supported environment variable names with the reported SCHEMING__DATASET_SCHEMAS and CKAN__SCHEMING__DATASET_SCHEMAS settings. Done means the endpoint returns the configured schema instead of an empty result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100