Content of our blog
Find a file
2024-12-17 15:20:01 +01:00
articles Minor changes to sponsors article 2024-12-17 15:20:01 +01:00
bin Set blog title of /tags to "Tags" 2024-10-28 18:55:57 +01:00
css css: ok, it looks better with background-color higlighting 2024-10-09 12:10:14 +02:00
images Add article about elit 2024-10-26 11:21:04 +02:00
js First commit 2023-11-13 19:13:44 +01:00
pages First commit 2023-11-13 19:13:44 +01:00
templates in layout, use the '-' instead of undefined '{{dash}}'. fixes #5 (or at least works around it) 2024-10-28 18:40:49 +01:00
.gitignore Upgrade to the unreleased version of YOCaml 2 2024-09-30 20:39:49 +02:00
blogger.opam Generate the commit message with the actual commit of main 2024-10-25 17:52:13 +02:00
dune-project Depend on dune 3.16 2024-10-04 13:15:13 +02:00
LICENSE First commit 2023-11-13 19:13:44 +01:00
README.md minor documentation updates 2024-10-28 18:10:05 +01:00
update.sh minor documentation updates 2024-10-28 18:10:05 +01:00

How to add an article?

The Git repository contains 2 branches:

  • the main branch which has the blog engine
  • the gh-pages (as GitHub) which contains the generated website

The user can have an overview of the website via:

$ git clone git@git.robur.coop:robur/blog.robur.coop
$ cd blog.robur.coop/
$ opam pin add -yn .
$ opam install --deps-only blogger
$ dune exec bin/watch.exe --

A little server run on http://localhost:8000.

The user can add an article into the articles/ directory. The format is easy. A simple header which starts with --- and finish with ---. Inside, you have a YAML description of the article where some fields are required:

  • date
  • title
  • description
  • tags

You can specify an author (with its name, email and link) or not. By default, we use team@robur.coop. If everything looks good, you can generate via the blogger.exe tool the generated website via:

$ dune exec bin/push.exe -- push \
  -r git@git.robur.coop:robur/blog.robur.coop.git#gh-pages \
  --host https://blog.robur.coop
  [--name "The Robur team"] \
  [--email team@robur.coop]

An SSH communication will starts. If you already registered your private key with ssh-agent and your .ssh/config is configured to take this one if you communicate with with git@git.robur.coop, everything will be smooth! Et voilà! At the end, an HTTP request will be send to https://blog.robur.coop (via Forgejo) to update the unikernel with the last version of the blog.

You can also use the update.sh script to update the blog with the builder user on the server machine.

NOTE: don't forget #gh-pages! Also, you probably should do a git pull.