You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should do the Hugo build on the server instead and not to commit it to the production folder.
We should also trigger the build via a webhook when a push to master is done.
We should also keep the hugo sources in a subfolder and keep the deploy program and the content negotiator and the nginx config (at least the redirects that will be included in the master config) in other folders.
The text was updated successfully, but these errors were encountered:
sounds like an excellent idea. I always thought it strange to put generated content under SCM, and it clutters your working copy with stuff you can't edit.
I think we should do the Hugo build on the server instead and not to commit it to the production folder.
We should also trigger the build via a webhook when a push to master is done.
We should also keep the hugo sources in a subfolder and keep the deploy program and the content negotiator and the nginx config (at least the redirects that will be included in the master config) in other folders.
The text was updated successfully, but these errors were encountered: