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
Faster turn-around times for devs using containers #9590
Comments
We talked about this about 45 minutes into today's container meeting: https://ct.gdcc.io |
I'm just noting that today (and last Friday), I've been hacking around in xhtml and the feedback loop is unbearable with containers. I'm going to install Payara 6 directly on my Mac so I can hack on xhtml and have it deployed by Netbeans basically instantaneously. (Later...) @poikilotherm and I played around with this. We observe that Netbeans copies the src xhtml into the exploded war:
We tried this:
Still not quite working. Stay tuned! 😅 |
By mounting the directory that contains the web application as an exploded WAR, we can enable hot redeploys of code and XHTML. To enable version-agnostic mounts, the output directory is configured to not contain the version number anymore, but the WAR file is still containing it.
By mounting the directory that contains the web application as an exploded WAR, we can enable hot redeploys of code and XHTML. To enable version-agnostic mounts, the output directory is configured to not contain the version number anymore, but the WAR file is still containing it.
- Use caddy as a faster and smaller alternative to NGINX. - Remove unnecessary pom.xml entry for container. - Migrate config to Caddyfile in /conf instead of /modules (we do not create a new image here...) - Add dependency on Dataverse container to proxy container - Slight renaming of containers
It might be good to keep it available on localhost in addition to the HTTP variant on port 4848 via proxy.
With using the env var "SKIP_DEPLOY" or the Maven property "-Dapp.deploy.skip" we can make the application server not deploy Dataverse on container start. This is necessary to save on time and manual undeploy when using Payara IDE tools to hot deploy changes.
sphinx-tabs upgraded to be compatible with v7. DATAVERSE_JSF_REFRESH_PERIOD restored (not sure why it was removed). Conflicts: doc/sphinx-guides/requirements.txt doc/sphinx-guides/source/conf.py docker-compose-dev.yml
Part of the containerization strategy, milestone D.
With #9584 we will recommend stopping, repackaging and start all containers again after code changes. This takes, depending on your local hardware, 60-120 seconds. Investigate in making this faster is the task of this issue.
The text was updated successfully, but these errors were encountered: