Problem installing extensions in dev mode
- Dominant language
- Shell
- Stars
- 151
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I successfully setup a docker compose based dev environment. Now, I want to add some extensions to instance, but was not successfull, maybe I missed something.
I "git cloned" the extensions into the src folder (for example, the "scheming" extension). Then, I run bin/install_src and it ended up successfully:
Successfully built ckanext-scheming
Installing collected packages: ckanext-scheming
Successfully installed ckanext-scheming-3.1.0
Now, in the .env file, I changed/added (the file ckan_dataset.json lies beside the scheming extension):
CKAN__PLUGINS="image_view text_view datatables_view datastore datapusher envvars scheming_datasets"
scheming.dataset_schemas = ckanext.scheming:ckan_dataset.json
After restarting the whole docker compose stack (or using the commands in bin), the scheming is not active. Taking a look at the logs of the Docker container, I can see that it seems to use /srv/app/ckan.ini (an empty default?) as config and not the stuff from the .env file:
[prerun] Setting the following plugins in /srv/app/ckan.ini:
image_view text_view datatables_view datastore datapusher envvars
Thanks for any help!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading bin/install_src and the Docker startup output around [prerun], then compare the .env values with the generated /srv/app/ckan.ini. Reproduce the setup with ckanext-scheming, CKAN__PLUGINS, and scheming.dataset_schemas; it is done when the generated configuration includes the requested plugin and schema setting after restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100