feat: add post number in slugs

This commit is contained in:
Bruno Carlin 2025-06-16 02:38:40 +02:00
parent d480ecb5cd
commit 839606f70c
WARNING! Although there is a key with this ID in the database it does not verify this commit! This commit is SUSPICIOUS.
GPG key ID: 8E254EA0FFEB9B6D
7 changed files with 10 additions and 19 deletions

View file

@ -4,7 +4,7 @@ date: "2010-09-15T00:00:00+02:00"
tags:
- Nginx
- Mediawiki
slug: setup-nginx-for-mediawiki
slug: 1-setup-nginx-for-mediawiki
summary: >
A simple configuration to serve Mediawiki with Nginx and FastCGI
---

View file

@ -2,7 +2,7 @@
title: Build the latest PgPool-II on Debian Etch
date: "2010-12-14T00:00:00+01:00"
tags: [Debian, PgPool-II]
slug: build-pgpool-on-debian
slug: 2-build-pgpool-on-debian
summary: >
Building PgPool-II on RHEL 5.5 to avoid the "libpq is not installed or
libpq is old" error

View file

@ -1,5 +1,5 @@
---
slug: aptana-eclipse-and-xulrunner
slug: 3-aptana-eclipse-and-xulrunner
title: Aptana Studio/Eclipse and Xulrunner
tags: [Aptana Studio, Eclipse, Xulrunner, Arch Linux]
date: "2011-12-16T00:00:00+01:00"

View file

@ -1,6 +1,6 @@
---
tags: [Python, Buzhug, Database, Locks]
slug: locking-buzhug
slug: 4-locking-buzhug
title: Locking Buzhug
date: "2012-02-07T00:00:00+01:00"
summary: >
@ -13,8 +13,7 @@ a few gotchas.
[Buzhug]: http://buzhug.sourceforge.net
Simple solutions are often the best
===================================
## Simple Solutions Are Often The Bests
I came to use Buzhug for the following requirements:
@ -37,10 +36,7 @@ After a quick prototyping (1 day), the choice was done.
Then came a few weeks of development and the first stress tests...
And the real world came back fast
=================================
## And The Real World Came Back Fast
A few times a day, the application backed by this database is intensely used:
@ -54,9 +50,7 @@ Using `buzhug.TS_Base` instead of `buzhug.Base` did not solve anything,
as the problem is not thread, but processes. What I need is a system-wide
cross-process lock.
Here is the answer
==================
## Here Is The Answer
First step was to find how to implement a cross-process, system-wide lock.
As it only has to work on Linux, the
@ -64,7 +58,6 @@ As it only has to work on Linux, the
Vmfarms](http://blog.vmfarms.com/2011/03/cross-process-locking-and.html) fits
perfectly. Here is a version slightly modified to make it a context manager :
{{< highlight python >}}
import fcntl
@ -99,7 +92,6 @@ class PsLock:
The second step is to define a new class that inheritates from `buzhug.Base`
that uses `PsLock` (inspired by `TS_Base`):
{{< highlight python >}}
import buzhug
@ -174,5 +166,4 @@ Now I just use
database = PS_Base( ... )
{{< /highlight >}}
And all the errors have vanished.

View file

@ -1,6 +1,6 @@
---
tags: [Sublime Text 2]
slug: automatically-open-sublime-text-projects-in-a-directory
slug: 5-automatically-open-sublime-text-projects-in-a-directory
title: Automatically open Sublime Text projects in a directory
date: "2013-05-15T00:00:00+02:00"
summary: >

View file

@ -1,6 +1,6 @@
---
title: Discourse without Docker
slug: discourse-without-docker
slug: 6-discourse-without-docker
date: "2016-06-27T00:00:00+02:00"
tags: [discourse, docker]
summary: Detailed instructions on how to install Discourse and plugins without Docker.

View file

@ -1,6 +1,6 @@
---
title: 'Prepare for the Next Internet Outage'
slug: 'prepare-for-the-next-internet-outage'
slug: '7-prepare-for-the-next-internet-outage'
date: '2025-06-14T04:05:48+02:00'
tags: [architecture, cloud]
summary: >