Deployment
We need a way to deploy the thing. Ideally it'd simply entail giving our clients the binary, player.js, *.css files and a config file, instructing them to tweak the config to their liking and schedule the binary to run every so often, or when triggered by pushes to the repo.
The binary itself should be able to:
- Pull the *.hmml files from their configured repo
-
Pull the quotes from insobot's store: https://dev.abaines.me.uk/quotes/name.raw
- cURL the quotes
- Search the quotes
- Pull from and push to the reference store
- Push to cinera_topics.css
- Put the converted index.html files in their configured directories
-
Push to and pull from the main index file
- Basic index file that enables generation of a Table of Contents for one project
- Multiple projects per index file
- Smart index file that enables fast searching / filtering
- Trigger the client site's own generator for integration of our stuff
The config file should be hot-reloadable, and will require:
- Edition setting, i.e. %Single Edition, %Project Edition or %Network Edition
- Directory paths
- Output URL naming scheme
- Personelle – hosts, guests and annotators – credentials, i.e. full name, homepage URL, financial support platform / URL
- Repo login credentials
- Exposing member / project data