.editorconfig
run `v init` to add the missing .editorconfig, .gitattributes and most importantly v.mod
3 years ago
139 bytes
.gitattributes
run `v init` to add the missing .editorconfig, .gitattributes and most importantly v.mod
3 years ago
172 bytes
issue_routes.v
issues: card-style posts, sidebar tabs with mentioned/activity feeds
last May 16
6.36 KB
main.v
delete repo confirm modal; header/settings i18n; add es/jp/cn/pt languages; issue title markdown; tree poller path
last May 16
2.53 KB
1 MiB
Gitly
GitHub/GitLab alternative written in V.
https://gitly.org
- Light and fast
- Minimal amount of RAM usage (works great on the cheapest $3.5 AWS Lightsail instance)
- Easy to deploy (a single <1 MB binary that includes compiled templates)
- Works without JavaScript
- Detailed language stats for each directory
- "Top files" feature to give an overview of the projectThis is beta softwareThe V web framework and Gitly are at an early stage of development. Lots of features are missing. The biggest missing features that will be implemented soon:
- [x] Multiple users and multiple repos
- [x]
git push - [ ] Access via ssh
- [ ] Pull requests
Gitly builds against PostgreSQL by default. Create the default PostgreSQL role/database with:v build.vsh ./gitly
To build a SQLite-backed binary instead, use:v run setup_db.vsh
The SQLite database path defaults tov -d sqlite . ./gitlygitly.sqliteand can be changed withsqlite.pathinconfig.jsonorGITLY_SQLITE_PATH. PostgreSQL settings can be changed withpginconfig.json,GITLY_DB_*environment variables, or the usualPG*environment variables.If you don't want to installsassc, you can simply run
Required dependencies:curl https://gitly.org/css/gitly.css --output static/css/gitly.css
- V 0.4.2 93ff40a (https://vlang.io)
- SQLite (Ubuntu/Debian:
libsqlite3-dev) - PostgreSQL client library (Ubuntu/Debian:
libpq-dev, macOS:brew install libpq) - Markdown (
v install markdown) - sassc
Features
- Track performance in CI (e.g. compare certain binary performance across different commits)
- Run only certain actions for commits (e.g. you're a fixing a bug that involves only a certain OS, and you don't want to wait for other CI)
- Prioritize CI runs (e.g. this PR must be handled first, then the rest)
- "Top files" mode
- Release files can only be generated by CI/CD, with the version of the tree used always available. This prevents malware binaries.
