Tools allowing to keep sans.pub up-to-date and automate common recurring actions.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Pierre Martin 204efe8a8b feat(caprover): allow human to mark an app as successfully updated 2 months ago
domain feat(caprover): allow human to mark an app as successfully updated 2 months ago
infrastructure feat(caprover): allow human to mark an app as successfully updated 2 months ago
routes feat(caprover): allow human to mark an app as successfully updated 2 months ago
services feat(caprover): allow human to mark an app as successfully updated 2 months ago
ui feat(caprover): allow human to mark an app as successfully updated 2 months ago
.gitignore feat: initial mini simple event sourcing for pending application updates 3 months ago
LICENSE Initial commit 12 months ago
Makefile test: add TS checks and fix issues 2 months ago
README.md feat(cli): add a `captain-update` script to generate a report of all applications to update 12 months ago
bun.lockb feat(caprover): allow to trigger an application update 2 months ago
joe.ts feat(caprover): allow human to mark an app as successfully updated 2 months ago
package.json test: add TS checks and fix issues 2 months ago
tsconfig.json feat(caprover): allow to trigger an application update 2 months ago

README.md

Tools

Tools allowing to keep sans.pub up-to-date and automate common recurring actions.

captain-update.mjs

Allow to generate a report of all versions of applications deployed on sans.pub, with the current status of each application and whether they need an update or not.

It can serve as a base for a changelog entry, and as a TODO list for updating applications.

Example:

CAPTAIN_DOMAIN=xxxx CAPTAIN_PASSWORD='yyy' ./captain-update.mjs > /path/to/site/src/changelog/2023-05-08.md

TODO

  • try to update applications automatically from a prompt