Add files for building documentation into a Docker image for web serving. #186
No reviewers
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#186
Loading…
Reference in New Issue
No description provided.
Delete Branch "docs-image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Most of this was transplanted from a separate repository that contains the whole torsion.org site contents. My motivation for moving this is that, eventually, I'd like to put the building and deployment of borgmatic docs directly into CI so that it's a more automated process. This is a first step in that direction, in that it moves borgmatic-specific content into the borgmatic repository.
In terms of the Docker image itself, its content comes from a static site generator called Eleventy. The files in this PR are config, templates, and CSS necessary to make Eleventy work, plus a Dockerfile and a couple of bash scripts to tie it all together. In the future, some of this could be added to CI and run automatically.
Testing: Rejiggered the external torsion.org provisioning to make use of this new borgmatic docs image for everything in the https://torsion.org/borgmatic/ URL space. Ran provisioning (Ansible + Docker Compose), and observed that the borgmatic web site still works.
Grea idea.