To reproduce, first make some changes in order to actually be able to run ckan 2.8 with docker-compose here. I pushed those to https://github.com/pazepaze/docker-ckan/tree/2.8-working-setup (Sidenote: it should probably be documented somewhere how to run the other ckan versions supported in this repo)
Then run normally with
docker-compose build && docker-compose up -d
Create a dataset and upload the following simple csv file:
foo,bar
1,2
3,4
The datapusher will not be triggered automatically. If you go to the resource > Manage > Datastore though, where you can see the Upload log in the ckan UI, something strange happens: If you hammer F5 in the browser a few times to update that page, the datapusher can finally be convinced to upload the file.
Datapusher does not upload csv automatically anymore after recent update to the datapusher Dockerfile.
I found this new behavior on my ckan 2.8 setup after pulling your changes to the Dockerfile. I was using https://github.com/okfn/docker-ckan/commit/96f46d45000b54e7c749a92e32a91796923fa633 before.
To reproduce, first make some changes in order to actually be able to run ckan 2.8 with docker-compose here. I pushed those to https://github.com/pazepaze/docker-ckan/tree/2.8-working-setup (Sidenote: it should probably be documented somewhere how to run the other ckan versions supported in this repo) Then run normally with
Create a dataset and upload the following simple csv file:
The datapusher will not be triggered automatically. If you go to the resource > Manage > Datastore though, where you can see the Upload log in the ckan UI, something strange happens: If you hammer F5 in the browser a few times to update that page, the datapusher can finally be convinced to upload the file.
Not sure whether this is a datapusher issue or an issue with the datapusher dockerfile here. All I can say is that it worked with the datapusher Dockerfile from commit https://github.com/okfn/docker-ckan/commit/96f46d45000b54e7c749a92e32a91796923fa633 (before the changes in October 2020).