Content of our blog
Find a file
Reynir Björnsson 3b1d9f0805 Implement tags
All tags are now on a single page. This is easier to implement with
yocaml2's architecture.
2024-10-09 11:51:14 +02:00
articles Upgrade to the unreleased version of YOCaml 2 2024-09-30 20:39:49 +02:00
bin Implement tags 2024-10-09 11:51:14 +02:00
css First commit 2023-11-13 19:13:44 +01:00
images EC article 2024-02-13 16:37:29 +01:00
js First commit 2023-11-13 19:13:44 +01:00
pages First commit 2023-11-13 19:13:44 +01:00
templates Implement tags 2024-10-09 11:51:14 +02:00
.gitignore Upgrade to the unreleased version of YOCaml 2 2024-09-30 20:39:49 +02:00
blogger.opam Depend on dune 3.16 2024-10-04 13:15: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 Upgrade to the unreleased version of YOCaml 2 2024-09-30 20:39:49 +02:00
update.sh Upgrade to the unreleased version of YOCaml 2 2024-09-30 20:39:49 +02: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 src/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 src/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 Gitea) 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.