blog.iscsc.fr: a blog built with HUGO framework

TODO

Non-exhaustive TODO-list:

• write a workflow that prevents merging if website doesn't build
• fix nginx.conf and run_nginx.sh properly
• Add automatic deployment on push to src/**
• write a workflow warning if the new content is still draft
• add https
• add posts from previous website
• add a comments engine
• fix baseUrl and "iScsc" sidebar brand name not redirecting
• print a lastUpdate or updated date param on posts
• show posts which draft param is true in dev mode (if possible)
• check when building (with builder target) that git submodule is updated

Features

• renders emojis https://emojibase.dev/shortcodes/?

Deployment

Production

Create SSL certification

To set up HTTPS, you will need valid SSL certificates. If you deploy the app for the first time, follow these instructions:

• Comment or delete the whole server section about 443 in the nginx.conf file.

- server {
- listen 443 default_server ssl http2;
- ...
- }

This step is required because the certificates don't exist yet, so they cannot be loaded in the nginx configuration.
The website has to run with http to respond to certbot challenge

• (Re)Start the blog container:

docker compose up --detach --build blog

• Create the certificates with the certbot container:

docker compose run --rm certbot certonly --webroot --webroot-path /var/www/certbot/ -d yourdomainname.com

• Restore the original nginx.conf (with git restore nginx.conf for example)
• Stop the blog container:

docker compose down

The certificates should have been generated in certbot/conf/live/yourdomainname.com/.

Renew SSL certification

If you just want to renew existing certificates, use:

docker compose run --rm certbot renew

Deploy the website itself

Create the blog/prod directory, it must be writable by users that will write to it: you, builder target, CI user...

mkdir -p build/blog/prod
chmod <make it writable by the appropriate user/group>
chown <make it owned by the appropriate user/group>

you should check first the consistency of the server name (iscsc.fr/localhost) in those files: nginx.conf, ...

Start the nginx container to serve requests:

docker compose build blog
docker compose up --detach blog

Note: before the next step make sure that when cloning the repository you also updated the git submodule!

Then builds the static website, ./build/blog/prod is a volume shared with both containers so building the website will automatically "update" it for nginx.

docker compose up builder

Automatic deployment

The repository contains a GitHub Actions which automatically:

1. builds the website: allow to check that nothing is broken, publish an artifact which can be downloaded or reused
2. IF push to main AND src/* modified, deploys the build: download the artifact, create and setup ssh key, send build to server through ssh (with rsync)

This requires a server (a VPS) ready to receive the build (and to be useful, running a http server serving this build), and, of course, to set some mandatory GitHub secrets (ssh key, CI username on server, path,...).

Sources I used:

• Scott W. Harden's tuto
• HUGO deocumentation
• GitHub Actions documentation

Development

it requires hugo installed locally!

cd src
hugo server --buildDrafts --buildFuture

--buildFuture is also used in production, --buildDrafts only in development
--buildExpired can be used too

This will build sources and start a basic development server that listens on http://localhost:1313.

The HUGO server automatically watches sources, so if you create a new post while it's running it will automatically rebuild the website and serve the new post.