Queen guards the kitten den.
| assets | ||
| migrations | ||
| src | ||
| templates | ||
| .env.example | ||
| .gitignore | ||
| .rustfmt.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| queenie.service | ||
| README.md | ||
Queen
Setting up dev environment
Copy the .env.example to .env then fill in missing variables:
cp .env.example .env
Use sqlx-cli (install using cargo install sqlx-cli) to create and migrate the database:
sqlx db create ; sqlx migrate run
Development
Run the server for development:
cargo run -- -e .env
The -e (or --env) option tells Queenie where to find its environment configuration file; the
default is /etc/forgejo/queenie.env.
The assets used in Queen come from forgejo,
so you can use a local Caddyfile to serve both forgejo and queen
(assuming that forgejo is running on localhost:3000):
{
http_port 9000
}
localhost:9000 {
reverse_proxy /signup* localhost:4008
reverse_proxy /payment_success* localhost:4008
reverse_proxy localhost:3000
}
Run caddy with:
caddy run --config Caddyfile
Use in production
There's a sample systemd unit file, queenie.service.