Hugo CMS

[nebulon]

@fbartels That is indeed true, I was thinking of adding checksum tests though, but for now the sync already helps to purge files on the remote end, which don't exist anymore in a new build. Of course if the pipeline is used to build artifacts or packages, then the old surfer put should be used to not purge the old ones

[fbartels]

@nebulon I noticed that in newer surfer version you added some parallelization for put requests. Upgrading surfer to the lastest version brought the deployment time down to four minutes.

[vjvanjungg]

@jdaviescoates check out my new guide https://forum.cloudron.io/topic/4042/beginner-s-guide-hugo-gitlab-ci-surfer hope it helps you get up and running.

[doodlemania2]

@vjvanjungg Very nicely done!

[timconsidine]

Sorry to revisit this old topic
Fully appreciate about static site generators building locally and push-publishing remotely.

But there’s an element to the discussion missing. In my case, I don’t want to be building locally. Then I am tied to a specific local device. It may not be to hand (and maybe too lazy to levitate posterior from sofa).

Yes, I could sync local configs between devices, but that’s not always smooth.

I would prefer to use a cloud resource to build and publish. If I am working in the terminal locally, no different to working in terminal remotely.
Yes, I could setup a remote deployment of a Linux desktop, use that to build and publish to eg Surfer. But why the duplication ? Seems more elegant and contained to be able to do it in one place.

I know this is contrary to the CI/CD bandwagon. But I see a lot of advantages, principally avoiding multiple component pieces.

[girish]

@timconsidine afaik, hugo is a CLI tool. One has to write a web application that you ask for - something which accepts git pushes or accepts uploads or monitors some git repo etc and then builds via hugo.

To be fair, this is what we did with GitHub Pages app . It runs jekyll and accepts git pushes (but only via http)

[timconsidine]

@girish hugo is CLI for building and outputting the built files.
Totally happy with building the site pages in terminal, rendering them in Hugo, using webserver to serve.
I just want to do it all in one container, without CI/CD, cloning repos, pushing files.
Maybe I will try a custom image based on Surfer.

[robi]

@timconsidine are there not hugo web front ends that might help?

[girish]

@timconsidine Depending on your use case:

• Install surfer
• Install hugo into /app/data of surfer - https://gohugo.io/installation/linux/
• Then, setup a cron script via https://docs.cloudron.io/apps/#cron . That cron script periodically checks for changes in upstream, builds it locally and copies over to the surfer directory.

[robi]

And you can mount Surfer app remotely via webdav!

[timconsidine]

@girish thank you, I have taken a very similar but slightly different approach :

• taken cloudron surfer as base app
• tweaked Dockerfile to install hugo (into /app/data as suggested)
• added a deploy.sh script for manual publishing (not via cron)

Installed it as a custom app.
Works nicely (as of course it should)
Need to tidy it up before publishing a repo.

So now I have Hugo bundled with Surfer, so all coding & building can be done within the container/app deployment.
No need for CI/CD, and no need for git commits / push / fetch etc.
Just open up the terminal from the app's settings panel.
Single 'source of truth' accessible from any device.

It might be a niche use case, but if someone really wants hugo deployed on Cloudron, it's available.