No description
Find a file
2024-12-29 16:09:08 -06:00
docs add privileged parameter for jobs and improve docs 2024-12-26 19:55:49 -06:00
src add test for the config thing and improve docs a bit 2024-12-27 20:42:11 -06:00
.gitignore initial commit - has sort tests 2024-12-17 23:01:46 -06:00
Cargo.lock add reading config, add and update docs 2024-12-26 12:18:16 -06:00
Cargo.toml add reading config, add and update docs 2024-12-26 12:18:16 -06:00
gregory.example.yml update example yaml to actually be runnable 2024-12-29 16:08:59 -06:00
README.md update todo 2024-12-29 16:09:08 -06:00

Gregory

This is Gregory. Gregory controls repos. Gregory keeps track of updating repos, trying to be simple and elegant, but enough.

Documentation

Go look at docs/

TODO

  • Add sources (similar to sources in a PKGBUILD)?
  • Add support for loading scripts rather than listing commands
  • Add multithreading
  • Add better/custom grouping for when to run jobs (dependency system?)
  • Add dependency system (automatic detection?)
  • Add hook system
  • Add SQL database (maybe using sqlx?)

Other stuff

  • The formatting for the config file (gregory.yml) was heavily inspired by Drone's config.
  • Why the name?
    • I was thinking to go with something dark and foreboding, since this is a program to control everything about a repo - it's the high command. But I couldn't think of anything and thought just naming it some lame random name instead would be way funnier. Hence, Gregory.
  • Gregory is a program, so it uses it/its pronouns. It also doesn't mind whether you capitalize its name or not, "gregory" or "Gregory" are fine, you can even shorten it if you want.