-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup datastore and datapusher #27
Comments
@lpasquali please make sure you have all the info you need to move on with the task and assign an estimate to the issue so we can schedule it. Make changes to the checklist as needed |
Official doc here: This is the config of the datapusher image in the official docker-compose: In the The datastore DB should already be set, anyway make sure that it can be properly accessed by both the datapusher app and from inside CKAN (tabular data should be displayed in a grid -- current deploy is not properly parsing the " |
|
@randomorder I think I can work on it, I put estimate |
@etj I think I implemented ckan datapusher/datastore plugins correctly. if I try to move data into the datastore the csv resources actually do become correctly formatted as stated above #27 (comment) also the "official" datapusher image is 4 years old: current upstream repository of datapusher is missing a Dockerfile but the code would support to setup MAX_CONTENT_LENGTH as env variable: https://github.com/ckan/datapusher I would suggest to add another submodule, for https://github.com/ckan/datapusher use Dockerfile from https://github.com/clementmouchet/datapusher and make our datapusher image, with more maintained datapusher code |
PR with work up to now: #35 |
It seems that the official ckan docker file references an old fork for the datapusher, which has not been updated in 6 years. Issue opened about this in the official repo: ckan/datapusher#228. Currently working on the dockerization of the master branch of the official repo: https://github.com/geosolutions-it/datapusher/tree/228_docker |
|
@etj unfortunately the code using datastore writing and read only users is not working for similar reasons we found in past:
ckan configuration of datastore database is correct, but the app itself is not able to determine the user even trying to escape, as in past the @ with %40, unfortunately the datastore code does not use ckan models for db |
Found some other issues in the datastore:
|
I'm going to check the issue in the datastore code |
updates @lpasquali ? |
Hello @etj did you get further on the datastore database (azure related) issues? |
please let us know @etj |
The datastore does not need any fix. psql -U $arg1@$arg3 -h $arg4 postgres -c "CREATE ROLE "datastore_ro@$arg3" NOCREATEDB NOCREATEROLE LOGIN PASSWORD '${arg5}';" instead of
It means you have to add the |
The |
I added a few commits to the The deploy procedure now completes successfully and ckan is properly launched. @lpasquali I guess this is unblocked now. |
please go ahead @lpasquali We need this before COB Friday |
I finally was able to get datastore, datapusher and their interactions working |
|
* implementation of datapusher/datastore plugins * implementation of datapusher container in azure compose, fixed readme * added new datapusher docker image, configured datastore, datapusher ckan plugins, initted datastore db * aligned datapusher submodule * aligned datapusher submodule * aligned datapusher in azure compose * removed unused module datapusher * fixed building compose in ckan-docker/docker-compose.yml * fixed building compose in ckan-docker/docker-compose.yml * reverted parameters * datastore db provision * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * changed psql command * pg for datastore * #39 make ckan config persistent * #39 make ckan config persistent * #39 make ckan config persistent * #39 make ckan config persistent * #27 fix datastore role creation * #27 fix datastore set-permission * #27 fix datastore role creation * parametrized sed * updated wrong image for datapusher on azure * datastore setup * updated wrong image for datapusher on azure * updated wrong image for datapusher on azure * updated wrong image for datapusher on azure * fixing datastore_ro privileges * fixing datastore_ro privileges * fixing datastore_ro privileges * fixing datastore_ro privileges * Provide APIKEY in command line * fixing datastore_ro privileges * fixing datastore_ro privileges * fixed after merge * last fixes * fixing datastore_ro privileges * wrong branch * revert to master branch * Use datapusher-datastore-ckan for testing * Reinstate grace-period plugin * Fix custom plugin order * Switch back to master branch Co-authored-by: etj <[email protected]> Co-authored-by: Emanuele Tajariol <[email protected]>
The text was updated successfully, but these errors were encountered: