No description

Find a file

askiiart 73ee302034 update id/revision to make sense/no dupes, add stderr to the example		2025-01-17 22:55:46 -06:00
.vscode	switch to toml	2024-12-29 23:10:29 -06:00
docs	update config file formatting (add dependencies, remove log-level)	2025-01-17 17:48:10 -06:00
src	update id/revision to make sense/no dupes, add stderr to the example	2025-01-17 22:55:46 -06:00
.gitignore	functional prototype	2024-12-29 16:31:56 -06:00
Cargo.lock	add start of error handling	2025-01-17 10:45:06 -06:00
Cargo.toml	add start of error handling	2025-01-17 10:45:06 -06:00
docker-compose.example.yml	add example postgres dompose file	2025-01-17 16:12:28 -06:00
gregory.example.toml	update id/revision to make sense/no dupes, add stderr to the example	2025-01-17 22:55:46 -06:00
podman-compose.example.yml	add start of error handling	2025-01-17 10:45:06 -06:00
README.md	update readme	2025-01-17 16:12:14 -06:00

Gregory

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

THIS IS A PROTOTYPE

Go look at docs/

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?

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.