-
-
Notifications
You must be signed in to change notification settings - Fork 96
Update troubleshoot.md - Entering Docker container, run classic commands #923
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
base: main
Are you sure you want to change the base?
Update troubleshoot.md - Entering Docker container, run classic commands #923
Conversation
β¦local zope commands for debugging Foot into the door from an answer to a ticket. To be enhanced as step 2β¦
@acsr if you have the opportunity to work with the trainers, would you please update this PR for accuracy and completeness? It seems to be in a draft state to me. It also has merge conflicts that you need to resolve. Please let me know. Thank you! |
@stevepiercy I have looked in to the state and cannot get at once the point how and why the merge conflict is displayed here in github. (I followed the Due to personal issues and no time I cannot follow the sprint in the next days as I would like. I confirmed the general wording of the purpose already. Lets see. |
I have reread the related issue plone/plone.exportimport#51 and the remarks by @yurj and I am not sure if I get the best approach to make serious suggestions to others in a generic way. I know that @fredvd suggested the use of firing up a dedicated container for the relstorage to filestorage conversion process. He wrapped this up during the Plone Tagung but do not see my skilllevel high enough to finalize the suggestion here. For me it was enough to get a classic Zope related command to work inside the docker container and recognizing the way to prefix the command with a call of |
Mentioned the challenge in this post + comment: https://community.plone.org/t/how-to-move-production-data-of-a-postgres-based-relstorage-from-a-currrent-cookieplone-based-docker-swarm-live-setup-to-a-similar-staging-site/22278/2 |
@acsr scroll to the end of the pull request. Observe how to resolve merge conflicts: ![]() |
Teaching implies a in my opinion outdated understanding of top down education. Some thing they cannot teach. Some hate teachers. The actual content of that pages reflect a more modern aproach and are more inviting. This should be also present in the wording of the TOC and Headlines. The content can also be improved to a more encouraging onboarding of trainers beyond it is already trying tis.
Corrected the component spelling while exporting it . Component was PloneReleaseView , and while exporting it was written as PlonereleaseView. I simply corrected the spelling. To save user's time from debugging small errors .
β¦ation part of Volto-hands-on training In the internationalisation part of the Volto hands on training,we have to first translate the Plone release content type of our site. The file to be updated is PloneReleaseView.jsx , but the training documentation says the file to be updated is plonerelease.jsx , which we never created in past. I corrected the file which should be updated-- (PloneReleaseView.jsx ,and not the non existent plonerelease.jsx) This can cause confusion to a new developer, and he might create a plonerelease.jsx which technically was PloneReleaseView.jsx .
To load an add-on, the project needs to specify the add-on in the addons key of package.json of main project. In the training , it was written project.json, I corrected it to package.json.
β¦Volto Version 17+
- Add genindex to toctree and home page - Sort conf.py to align with Documentation for easier future updates - Fix syntax errors - Purge unneeded JavaScript, since it was fixed upstream
Changed title capitalization
- Add `drag.svg` icon
The title needs a clarification and we need a second topic pointing to the latest available training / docs fort Plone 6 Classic / similar to Plone 5
Co-authored-by: Steve Piercy <[email protected]>
Co-authored-by: Steve Piercy <[email protected]>
fix typo
I believe this should be index.js not config.js.
Co-authored-by: Steve Piercy <[email protected]>
#968) Co-authored-by: Steve Piercy <[email protected]>
β¦local zope commands for debugging Foot into the door from an answer to a ticket. To be enhanced as step 2β¦
β¦-Docker-container
As @stevepiercy suggests I would like to have a review by a trainer experienced with docker containers for my change. Priority ReviewersThe trainings for Installing and Deploying Plone during 2025.ploneconf.org are held by @ericof & @fredvd. Maybe you look first. The approaches I wrote down came from input by @davisagli and @fredvd. @pbauer was relatively new to the deployment stuff when we fixed our building of images for ARM and troubleshoot the logs. @ksuess if you are into this you can also review this and tenor and scope. Finally having these tipps after heavily missing them was helpful for me. It is difficult to discover and filter for Plone as newbies with more complex docker setups. Actually the swarm approach is a good entry point when you get a grip at it. |
How to master running local zope commands for debugging inside a Docker container.
Foot into the door from an answer to a ticket. To be enhanced as step 2β¦
π Documentation preview π: https://plone-training--923.org.readthedocs.build/