|
|
|
|
|
by uberman
1290 days ago
|
|
Are you being instructed to push your repo to a build server and have it run Hugo and deploy the public folder to your webserver? That seems very reasonable. If you are being told to push your repo to the web server to have it do the build then that seems like a bad idea. For what it is worth, we use Hugo to build a public folder (build done in the cloud) that we deploy to a versioned tree on our web servers. When the build and deploy is done, we update the path that is being served. We tend to keep 3 releases handy so falling back is again just a simple webserver config change. |
|