tangentsoft/fossil repository overview

These images are built based on the Fossil⁠ project's stock Dockerfile⁠ using a custom build system⁠ to produce tagged images suitable for automated deployment with Podman⁠.

Image tags correspond to the upstream Fossil check-in names, in three forms:

• Version: At any one time, there's an image tagged with "version-*" which corresponds to the upstream Fossil release tagged the same way. I keep only the latest one since it's rare to have a good reason to be on anything older than the latest stable release.
• Check-In: The 12-character hex tags are a unique prefix of the upstream check-in ID⁠ used to generate the image. These are ephemeral builds made after the most recent release version to test new features, changes, and fixes. These all go away shortly after a release, reappearing as I make test builds along the way toward the upcoming release. I generally keep only the most recent build, plus the prior build as an emergency fallback.
• Latest: The "latest" tag is generally an alias for the most recent hex-tagged image, except in the short window between a release and the first test build, when it points to the release image.

This container expects the repository it serves to be called /museum/repo.fossil. This should be a bind-mounted directory and not a lone file⁠. This scheme incentivizes naming the enclosing directory more descriptively on the host side:

$ docker run \
    --publish localhost:9999:8080 \
    --name fossil-myproject \
    --volume ~/museum/myproject:/museum \
    tangentsoft/fossil

Binding the container to a high-numbered port on localhost like this is a good choice when putting it behind a front-end proxy of some sort, but this is merely one of several ways to set up a Fossil server⁠.

See the official documentation for this container⁠ for further details.