Add setup option and docs in projects README.md files to specify local server IP for development access to frontend from other machine than localhost #52
Labels
04 type: enhancement
making existing stuff better
12 prio: high
should be fixed soon
31 needs: help
anybody: please help with this issue
33 needs: docs
missing documentation: write it
No CSS served when developing from another machine
When starting the frontend using
make frontend-start
after initial setup the frontend is only reachable fully including styles from localhost:3000. Without further action you will get no CSS served externally e.g. using the IP of the server. In production behind a proxy this is sufficient and welcome. For development and testinstalls this sucks and the solution is not abvious.The Challenge
Fix is not obvious for newbies
After an initial attempt to install Plone6 Volto on a VM, WSL or external server via SSH this can be a serious frustration because hints to fix that issue are rare not in the official docs and community.plone.org hints were misleading and not clear in purpose and action to take.
How to avoid this already in Cookieplone
Instead of only mentioning this in the docs, avoiding the pitfall and offering the solution during Cookieplones setup will reduce frustration.
In Cookieplone the fully qualified domain name of the public site is already requested but not the local IP or fully qualified domain name of the server. If ending up for the same purpose it is not explained or added to the two README.md docs files (main project and and frontend) in the appropriate development section.
Suggestion:
In the Interactive Cookieplone session
In the generated Docs
Docs Part
Example:
Set the env variable HOST before or during issueing the
make
command to start the frontend.Start frontend
example:
This IP is listed at the end of the startup output of the frontend:
Then use this host address to open the Plone frontend on another machine in your local network:
http://192.168.168.123:3000
If in Development Mode make sure you open port 3001 in the firewall on the server as well, as it is needed for some Javascript code.
END of Example
ToDo
Add a corresponding proper part in the the Plone Documentation Installation Cookieplone project setup docs after https://6.docs.plone.org/install/create-project-cookieplone.html#start-plone as #troubleshooting-developer-access-from-other-ip
This is extremely useful for troubleshooting unexpected blockers after initial installs and avoid people leaving Plone with negative experience.
I answered already in these community.plone.org topics in a Q&D form:
[1] Volto repo is not loading stylesheets while running in localhost - Development / Plone 6 UI (Volto)
url:: https://community.plone.org/t/volto-repo-is-not-loading-stylesheets-while-running-in-localhost/16111
tags:: #[[CSS]], #[[Environment Variables]], #[[Firewall]], #[[Plone]], #[[Plone6]], #[[Plone6 Volto]], #[[Stylesheets]], #[[Troubleshooting]], #[[Volto]], #[[Volto Frontend]]
[2] Volto load but no styles (New to Volto)
url:: https://community.plone.org/t/volto-load-but-no-styles-new-to-volto/20001
tags:: #[[CSS]], #[[Environment Variables]], #[[Firewall]], #[[Plone]], #[[Plone6]], #[[Plone6 Volto]], #[[Stylesheets]], #[[Troubleshooting]], #[[Volto]], #[[Volto Frontend]]
Only somehow related is this and can be mentioned in the same context as well:
[3] Unable to connect to Frontend in Plone 6 - Development / Plone 6 UI (Volto)
url:: https://community.plone.org/t/unable-to-connect-to-frontend-in-plone-6/15970
tags:: #[[Environment Variables]], #[[Firewall]], #[[Javascript]], #[[Plone]], #[[Plone6]], #[[Plone6 Volto]], #[[Stylesheets]], #[[Troubleshooting]], #[[Volto]], #[[Volto Frontend]]
The text was updated successfully, but these errors were encountered: