There are 2 kinds of access to the HydePark:
TL; DR — use the contact form
There’s no “join” form. You simply use the contact form and send us:
- The username you want.
- A password (for read-only web access).
- [If you also want to edit things] — a public SSH key.
If you’re not sure you’ll create or edit sites here (or what an SSH key is 😉), you can skip the last bit (we can always do that later).
Remember to leave an email address, or some other way to contact you.
Username should be a valid url slug
Once you have a username and a password, you can use it anywhere
at the HydePark ( i.e. all URLS beginning with https://swatwt.com/hydepark ).
This doesn’t mean you’re allowed to see everything there. It’s up to Alice
to decide which users can see
/hydepark/alice/someproject/preview. By default,
access would be global (i.e. not public, but everyone with a HydePark password
has read permissions). If
hydepark/alice/someprojects/surprise-branch are sensitive, Alice can limit read
access to specific users, so if you can’t access something under
— ask Alice to give you permissions.
git remote add gito email@example.com:alice/mynewproject
ssh -T firstname.lastname@example.org perms -l alice/mynewproject
email@example.com. Gitolite can tell us apart because we have different ssh keys.
Request a gitolite account
- Your username.
- A the password you want for reading (if you don’t have one yet).
- The content of the
.pubfile (not the other one 😱).
Hi. It's Alice (firstname.lastname@example.org). I do crosswords for Bob's new campaign, and I need an account. User: alice Password: mykewlpassword SSH key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDKtJ+5DXuUVMdr87D47mrTpkWU40UnGDt5yJjYjM9fquZtlIrZ8p7e4n8lTvIwXBuGsM29YgGjQ+VARQ6qMx/9PWItVsmG6iRBcA9qE45zJ6J0IhGB01RqqinCOezZ0Jk3bx/85JeKWmtpkfflLpyapocDRtcfiz9Yx4Ugr87IquOujB+ZbNbvLY3F+SQOEc2rc1LM945NRSAtvfqZC1946mAp9PEcOqtIl1v/xYMPDz+GjjigcRSrKgR3Mrv3r0KFwCK7roA/0617tiJehxoMCOgQxUubO6JeFFDxu6c9uAYH1lbTWcadqvSFGCkz+sqVD/4GGt8cfKTe0vBcbr9Z alice@home
The “email address” at the end of the SSH key doesn’t need to be a real one (be creative 😉),
but if you need to connect from several computers, you’ll need to sends a key for each,
so it may be useful to mark those keys with “email addresses”
Instead of addressing the server as
can simply call it
gito by adding this to
host gito hostname swatwt.com user zzzenolito
Now you can simply type commands like
git remote add gito gito:alice/mynewproject.
You can also add
alias gito='ssh -T gito' to your
and then you can simply type
gito perms -l alice/mynewproject
$ gito hello lito, this is zzzenolito@web48 running gitolite3 v3.6.2-20-g78fc240 on git 1.9.3 R W C CREATOR/..* # This means I [like all users] can create repos at my personal folder # ... all repos you have permissions for ... for example ... R lito/funnypage # Single-page sandbox site R lito/howto # This site # ... R lito/soliko # Hebrew single-page site # ... R W testing # A junk repo everyone has read/write access to # ... a few more lines, and then it hangs up $
As you can see, gitolite is not an interactive shell. You send it a command, it executes, KTHXBYE 😼
$ gito help # ... list of remote commands available: D create desc fork # ... $ gito desc -h # ... Usage: ssh git@host desc <repo> ssh git@host desc <repo> <description string> Show or set description for repo. You need to have write access to the repo and the 'writer-is-owner' option must be set for the repo, or it must be a user-created ('wild') repo and you must be the owner. # ...
In our case,
ssh git@host should be replaced with
ssh -T email@example.com (or simply
$ gito desc lito/funnypage Something simple to fork. https://swatwt.com/hydepark/lito/funnypage/preview/ # ...
You can also read about gitolite’s command line interface here.