sam.hadow/website-hadow.fr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

md improvement

Browse Source
This commit is contained in:
Sam Hadow
2025-11-16 22:27:51 +01:00
parent 49aee045ba
commit c03aebc605
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
_posts/2025-03-23-generate-a-website-with-jekyll.md
View File

@@ -15,26 +15,26 @@ One downside being it's obviously harder to handle interactions with clients sin
I decided to [install](https://jekyllrb.com/docs/installation/) a ruby development environment directly on my system, although you could use [containers](https://github.com/envygeeks/jekyll-docker/blob/master/README.md) is you prefer. I decided to [install](https://jekyllrb.com/docs/installation/) a ruby development environment directly on my system, although you could use [containers](https://github.com/envygeeks/jekyll-docker/blob/master/README.md) is you prefer.
I installed ruby and have the following in my .bashrc file to use gems (RubyGems) to use it as an unprivileged user and not the root user. I installed ruby and have the following in my .bashrc file to use gems (RubyGems) to use it as an unprivileged user and not the root user.
``` ```bash
# Install Ruby Gems to ~/gems # Install Ruby Gems to ~/gems
export GEM_HOME="$HOME/gems" export GEM_HOME="$HOME/gems"
export PATH="$HOME/.local/share/gem/ruby/3.0.0/bin:$PATH" export PATH="$HOME/.local/share/gem/ruby/3.0.0/bin:$PATH"
``` ```
To install Jekyll: To install Jekyll:
``` ```bash
gem install jekyll bundler gem install jekyll bundler
``` ```
(bundler is used to keep track of the depencies of each Ruby projects independently) (bundler is used to keep track of the depencies of each Ruby projects independently)
To create a new Jekyll project: To create a new Jekyll project:
``` ```bash
jekyll new site-name jekyll new site-name
cd site-name cd site-name
``` ```
Then during development I can just serve the website on a development machine and see if the results look good with: Then during development I can just serve the website on a development machine and see if the results look good with:
``` ```bash
bundle exec jekyll serve bundle exec jekyll serve
``` ```
If it looks good enough I can commit and push the website code and then deploy it on my server. To deploy it on my server I should automate things a bit more but for now I just have a make target to build the website and a make target to copy the files from _site to /var/www/html. If it looks good enough I can commit and push the website code and then deploy it on my server. To deploy it on my server I should automate things a bit more but for now I just have a make target to build the website and a make target to copy the files from _site to /var/www/html.

8
_posts/2025-11-02-nextcloud-collation-version-mismatch.md
View File

@@ -6,7 +6,7 @@ author: Sam Hadow
On my server I self-host nextcloud with a PostgreSQL database and this container image *docker.io/library/nextcloud:fpm-alpine*. On my server I self-host nextcloud with a PostgreSQL database and this container image *docker.io/library/nextcloud:fpm-alpine*.
You might encounter a collation version mismatch after upgrading Nextcloud or its base image and see messages like these in your logs: You might encounter a collation version mismatch after upgrading Nextcloud or its base image and see messages like these in your logs:
``` ```bash
2025-11-02 18:52:12.631 UTC [3514] WARNING: database "nextcloud" has a collation version mismatch 2025-11-02 18:52:12.631 UTC [3514] WARNING: database "nextcloud" has a collation version mismatch
2025-11-02 18:52:12.631 UTC [3514] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41. 2025-11-02 18:52:12.631 UTC [3514] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-02 18:52:12.631 UTC [3514] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE nextcloud REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. 2025-11-02 18:52:12.631 UTC [3514] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE nextcloud REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
@@ -26,13 +26,13 @@ You can follow this procedure to fix it:
### 1: Enable maintenance mode ### 1: Enable maintenance mode
The database must not be accessed during the procedure. The database must not be accessed during the procedure.
``` ```bash
podman exec -u www-data nextcloud-app php occ maintenance:mode --on podman exec -u www-data nextcloud-app php occ maintenance:mode --on
``` ```
Replace nextcloud-app with the name of your container. And use docker instead of podman if applicable. Replace nextcloud-app with the name of your container. And use docker instead of podman if applicable.
### 2: Rebuild the database indexes and refresh the collation version ### 2: Rebuild the database indexes and refresh the collation version
``` ```bash
podman exec -it nextcloud-db bash podman exec -it nextcloud-db bash
psql -U nextcloud nextcloud psql -U nextcloud nextcloud
REINDEX DATABASE nextcloud; REINDEX DATABASE nextcloud;
@@ -45,7 +45,7 @@ Log in to your nextcloud database and then reindex it, depending on the size of
The second command (`ALTER DATABASE ... REFRESH COLLATION VERSION`) just marks the collation version as current in PostgreSQL metadata and removes the warning. The second command (`ALTER DATABASE ... REFRESH COLLATION VERSION`) just marks the collation version as current in PostgreSQL metadata and removes the warning.
### 3: Disable maintenance mode ### 3: Disable maintenance mode
``` ```bash
podman exec -u www-data nextcloud-app php occ maintenance:mode --off podman exec -u www-data nextcloud-app php occ maintenance:mode --off
``` ```