askiiart/gregory
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
36 commits 1 branch 0 tags 348 KiB
Find a file
askiiart 339f93b95a
add postgres dev stuff
2025-01-23 20:08:00 -06:00
.vscode switch to toml 2024-12-29 23:10:29 -06:00
docs remove id and improve naming of logs 2025-01-18 15:14:28 -06:00
src fix docs 2025-01-23 13:16:06 -06:00
.gitignore add postgres dev stuff 2025-01-23 20:08:00 -06:00
Cargo.lock bump deps ig 2025-01-23 13:15:06 -06:00
Cargo.toml add start of error handling 2025-01-17 10:45:06 -06:00
gregory.example.toml remove id and improve naming of logs 2025-01-18 15:14:28 -06:00
podman-compose.dev.yml add postgres dev stuff 2025-01-23 20:08:00 -06:00
podman-compose.example.yml add start of error handling 2025-01-17 10:45:06 -06:00
README.md remove id and improve naming of logs 2025-01-18 15:14:28 -06:00

README.md

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 multithreading
  • Add hook system
  • Add SQL database (maybe using sqlx?)
    • Log stderr too
  • Add dependency system
    • Automatic detection with features (extensibility?) for each distro?
  • Add podman errors

Other stuff

  • The formatting for the config file (gregory.toml) 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.