- HTML 44.7%
- Rust 27%
- CSS 25.4%
- Dockerfile 2.2%
- Makefile 0.4%
- Other 0.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| .forgejo/workflows | ||
| media | ||
| migrations | ||
| src | ||
| static | ||
| style | ||
| templates | ||
| .dockerignore | ||
| .gitignore | ||
| .ignore | ||
| bacon.toml | ||
| build.rs | ||
| Cargo.toml | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
cement - a super light-weight pastebin
Cement is a very simple pastebin-like web application written in Rust.
Cement binds to the address 0.0.0.0 on port 3000. The address and port can be overridden with
the --host and --port flags (or HOST and PORT environment variable).
Cement stores pastes in a local or remote SQLite database, using libSQL. You can specify the
database file with the --db flag (or DB environment variable), or a remote URL and token with
the --db-remote and --db-token flags (or DB_REMOTE and DB_TOKEN environment variables).
$ cargo run -- --db /path/to/database.sqlite
$ cargo run -- --db-remote https://example.com/db --db-token 1234567890
Docker images are also available from two sources:
- Docker Hub: https://hub.docker.com/r/blakerain/cement
- Forgejo Registry: https://git.blakerain.com/BlakeRain/-/packages/container/cement/latest
You can pull the image and run Cement in a container, and use environment variables to configure
Cement. For example, to store the Cement database in a Docker volume called cement_data, you can
run the following commands:
$ docker volume create cement_data
$ docker run -p 3000:3000 -e DB=/data/cement.db -v cement_data:/data blakerain/cement