- Sponsor
-
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
Demo sites are empty #36
Comments
@pbauer @ericof I checked the setup, but create-site is already called from the Dockerfile as the default entrypoint. And the site is created, otherwise it wouldn't be online because the plonesite itself would not exist and the volto frontend would have nothing to contact. demo.plone.org/backend/Dockerfile Line 28 in 1de1cd4
I suspect something with the docker-entrypoint.sh script and the seleciton of the profile and distribution is not working out. installing the site locally now to debug. |
I can reproduce the issue locally, built the frontend from source, but the backend with 'make build-image'. then start the backend with my freshly built local image (replace the image_id):
But I don't get how this was runnign correctly before, becaus the create-site option just exits. The docker-entrypoint.sh comes from the official plone-backend image here: So if it only runs a script and then exits, the container is removed again and nothing happens. I wonder how this worked at all in the past. We could update the docker-entrypoint.sh script with a create-site-start case where we execute runwsgi from the start case after creating the site. |
The file |
The
I now simply renamed the script here thus replacing the default from plone-backend and it worked :) |
@pbauer I should have looked here before I tried to build locally (and, of course), it did work :-) |
Duh...... - vs _ :-) |
After the merge of #35 both demo-sites are empty:
https://demo.plone.org
https://classic.demo.plone.org
I guess
make create-site
needs to be added to the deployment-pipeline.The text was updated successfully, but these errors were encountered: