Fossil SCM
Improved the systemd guide's points about `podman generate systemd`.
Commit
ac30c2d9966f725845a11084778690cea8756e62ed815a2f69a8a843601f4b2d
Parent
117cf4ffe8ec6bf…
1 file changed
+8
-7
+8
-7
| --- www/server/debian/service.md | ||
| +++ www/server/debian/service.md | ||
| @@ -12,16 +12,18 @@ | ||
| 12 | 12 | |
| 13 | 13 | Two of the methods for running [containerized Fossil][cntdoc] integrate |
| 14 | 14 | with `systemd`, potentially obviating the more direct methods below: |
| 15 | 15 | |
| 16 | 16 | * If you take [the Podman method][podman] of running containerized |
| 17 | - Fossil, it opens the `podman create` option for you, exemplified in [the | |
| 18 | - `fslsrv` script][fslsrv] used on this author’s public Fossil-based | |
| 19 | - web site. That script pulls [custom containers][tscnt] from [my Docker | |
| 20 | - Hub repo][dhrepo]. With these elements combined, this scheme allows you to build | |
| 21 | - from source on one machine, then deploy to a server, running Fossil | |
| 22 | - containerized without needing build tools on the server. | |
| 17 | + Fossil, it opens the `podman generate systemd` option for you, as | |
| 18 | + exemplified in [the `fslsrv` script][fslsrv] used on this author’s | |
| 19 | + public Fossil-based web site. That script pulls its container images | |
| 20 | + from [my Docker Hub repo][dhrepo] to avoid the need for my public | |
| 21 | + Fossil server to have build tools and a copy of the Fossil source | |
| 22 | + tree. You’re welcome to use my images as-is, or you may use these | |
| 23 | + tools to bounce custom builds up through a separate container image | |
| 24 | + repo you manage. | |
| 23 | 25 | |
| 24 | 26 | * If you’re willing to give up [a lot of features][nsweak] relative to |
| 25 | 27 | Podman, and you’re willing to tolerate a lot more manual |
| 26 | 28 | administrivia, [the nspawn method][nspawn] has a lot less overhead, |
| 27 | 29 | being a direct feature of `systemd` itself. |
| @@ -34,11 +36,10 @@ | ||
| 34 | 36 | [dhrepo]: https://hub.docker.com/r/tangentsoft/fossil |
| 35 | 37 | [fslsrv]: https://tangentsoft.com/fossil/dir?name=bin |
| 36 | 38 | [nspawn]: ../../containers.md#nspawn |
| 37 | 39 | [nsweak]: ../../containers.md#nspawn-weaknesses |
| 38 | 40 | [podman]: ../../containers.md#podman |
| 39 | -[tscnt]: https://tangentsoft.com/fossil/dir/container | |
| 40 | 41 | |
| 41 | 42 | |
| 42 | 43 | ## User Service |
| 43 | 44 | |
| 44 | 45 | A fun thing you can easily do with `systemd` that you can’t directly do |
| 45 | 46 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -12,16 +12,18 @@ | |
| 12 | |
| 13 | Two of the methods for running [containerized Fossil][cntdoc] integrate |
| 14 | with `systemd`, potentially obviating the more direct methods below: |
| 15 | |
| 16 | * If you take [the Podman method][podman] of running containerized |
| 17 | Fossil, it opens the `podman create` option for you, exemplified in [the |
| 18 | `fslsrv` script][fslsrv] used on this author’s public Fossil-based |
| 19 | web site. That script pulls [custom containers][tscnt] from [my Docker |
| 20 | Hub repo][dhrepo]. With these elements combined, this scheme allows you to build |
| 21 | from source on one machine, then deploy to a server, running Fossil |
| 22 | containerized without needing build tools on the server. |
| 23 | |
| 24 | * If you’re willing to give up [a lot of features][nsweak] relative to |
| 25 | Podman, and you’re willing to tolerate a lot more manual |
| 26 | administrivia, [the nspawn method][nspawn] has a lot less overhead, |
| 27 | being a direct feature of `systemd` itself. |
| @@ -34,11 +36,10 @@ | |
| 34 | [dhrepo]: https://hub.docker.com/r/tangentsoft/fossil |
| 35 | [fslsrv]: https://tangentsoft.com/fossil/dir?name=bin |
| 36 | [nspawn]: ../../containers.md#nspawn |
| 37 | [nsweak]: ../../containers.md#nspawn-weaknesses |
| 38 | [podman]: ../../containers.md#podman |
| 39 | [tscnt]: https://tangentsoft.com/fossil/dir/container |
| 40 | |
| 41 | |
| 42 | ## User Service |
| 43 | |
| 44 | A fun thing you can easily do with `systemd` that you can’t directly do |
| 45 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -12,16 +12,18 @@ | |
| 12 | |
| 13 | Two of the methods for running [containerized Fossil][cntdoc] integrate |
| 14 | with `systemd`, potentially obviating the more direct methods below: |
| 15 | |
| 16 | * If you take [the Podman method][podman] of running containerized |
| 17 | Fossil, it opens the `podman generate systemd` option for you, as |
| 18 | exemplified in [the `fslsrv` script][fslsrv] used on this author’s |
| 19 | public Fossil-based web site. That script pulls its container images |
| 20 | from [my Docker Hub repo][dhrepo] to avoid the need for my public |
| 21 | Fossil server to have build tools and a copy of the Fossil source |
| 22 | tree. You’re welcome to use my images as-is, or you may use these |
| 23 | tools to bounce custom builds up through a separate container image |
| 24 | repo you manage. |
| 25 | |
| 26 | * If you’re willing to give up [a lot of features][nsweak] relative to |
| 27 | Podman, and you’re willing to tolerate a lot more manual |
| 28 | administrivia, [the nspawn method][nspawn] has a lot less overhead, |
| 29 | being a direct feature of `systemd` itself. |
| @@ -34,11 +36,10 @@ | |
| 36 | [dhrepo]: https://hub.docker.com/r/tangentsoft/fossil |
| 37 | [fslsrv]: https://tangentsoft.com/fossil/dir?name=bin |
| 38 | [nspawn]: ../../containers.md#nspawn |
| 39 | [nsweak]: ../../containers.md#nspawn-weaknesses |
| 40 | [podman]: ../../containers.md#podman |
| 41 | |
| 42 | |
| 43 | ## User Service |
| 44 | |
| 45 | A fun thing you can easily do with `systemd` that you can’t directly do |
| 46 |