Go to file
jolheiser fce5e40086
chore: remove dagger for now
It can be added back if I return to working on daggerserve

Signed-off-by: jolheiser <git@jolheiser.com>
2024-07-17 15:39:06 -05:00
.helix initial commit 2024-01-15 16:26:51 -06:00
assets initial commit 2024-01-15 16:26:51 -06:00
cmd/ugitd feat: native git 2024-02-22 13:14:05 -06:00
contrib feat: tags 2024-07-16 12:33:41 -05:00
internal feat: tags 2024-07-16 12:33:41 -05:00
.gitignore initial commit 2024-01-15 16:26:51 -06:00
LICENSE wip 2023-12-29 10:06:09 -06:00
README.md docs: update email 2024-05-24 21:08:39 -05:00
flake.lock feat: breadcrumbs and History.replaceState 2024-06-26 23:24:50 -05:00
flake.nix feat: convert to gomod2nix 2024-05-30 20:08:20 -05:00
go.mod chore: update go deps 2024-02-01 16:06:05 -06:00
go.mod.sri chore: update flake references and use gomodsri 2024-03-08 16:34:51 -06:00
go.sum chore: update go deps 2024-02-01 16:06:05 -06:00
gomod2nix.toml feat: convert to gomod2nix 2024-05-30 20:08:20 -05:00

README.md

ugit logo

ugit

Minimal git server

ugit allows cloning via HTTPS/SSH, but can only be pushed to via SSH.

There are no plans to directly support issues or PR workflows, although webhooks are planned and auxillary software may be created to facilitate these things. For now, if you wish to collaborate, please send me patches at ugit@jolheiser.com.

Currently all HTML is allowed in markdown, ugit is intended to be run by/for a trusted user.

Getting your public SSH keys from another forge

Using GitHub as an example (although Gitea/GitLab should have the same URL scheme)

Ba/sh

curl https://github.com/<username>.keys > path/to/authorized_keys

Nushell

http get https://github.com/<username>.keys | save --force path/to/authorized_keys

License

MIT

Lots of inspiration and some starting code used from gitea (MIT), wish (MIT), and legit (MIT).