Source code sharing (without breaking the back button)
Using a reverse proxy is the preferred method, there's a sample config in
contrib/nginx.conf where zig build run should just work.
But if you're unable to stand up a reverse proxy (a local proxy development
should be supported) you can try zig build run -- http to use http mode. Full
HTTP support is planned for "eventually" but no guarantees are made yet :)
Good luck!
In an unsorted order
-
srctree
- internal database upgrade scripts
- manual code sync
- view code
- public http clone
- view commits
- diff/code review
- CI API
- blame view for files
- blame view for dirs
- view history for file (navigable blame view)
- syntax highlighting (ish)
- native syntax highlighting
- README markdown support/formatting
- fold repo .files by default
- comment on commits
- email support
- outgoing email
- incoming email
- [-] submit diffs (works with special build step)
- open issues
- clone repo from remote
- set HEAD for newly clone repos
- auto pull from upstream
- auto push to downstream
- smart push/pull system
- auto create git branch for issues/diffs
- support for viewing branches
- network collection & browsing
- owner heat map
- owner activity journal
- commits
- anything other that
- user accounts
- new account setup
- git via ssh support
- Integration with other web VCS
- Improve CSS theme
-
verse
- typed templates
- custom types for templates
- basic logic for template system
- For
- ORNULL
- ORELSE "default"
- With
- Nested loops
- paired loops
- nested and paired loops
- docs for everything
- docs for template engine
- API for dynamic updates
-
git
- raw blob
- packed blob
- [-] tree/blob
- read
- write
- packed delta
- tags
- refs
- remotes
- git web (partial)
- PGP support
- commitish (see git.zig)
- .git repo init
- push/pull
- blame
- diff/patch generation