forked from
tangled.org/knot-docker
Docker config for @recaptime.dev's Knot server on Hack Club Nest.
knot.hackclub.community
chore(readme): update readme on where it hosted rn
Signed-off-by: Andrei Jiroh Halili <ajhalili2006@crew.recaptime.dev>
+4
-6
+4
-6
readme.md
+4
-6
readme.md
···
3
3
[](https://gitlab.com/recaptime-dev/infra/knot-server-docker/-/commits/recaptime-dev/main)
4
4
[](https://hackclub.com)
5
5
6
-
This is a knot server that Recap Time Squad uses to host our Git repositories on
7
-
[Tangled](https://tangled.org), hosted on [Nest](https://hackclub.app) for the
8
-
Hack Club community.
6
+
Sources for the container images of Tangled Knot server, used to run `knot.hackclub.community` at an Azure VM (previously on [Nest tilde server before going with Promox VM-based containers](https://hackclub.app)).
9
7
10
8
## Usage
11
9
···
16
14
# on its custom domain
17
15
git remote add origin ssh://git@knot.hackclub.community:33939/handle.host.tld/repo
18
16
19
-
# directly with Nest's hostname (since it's just a CNAME DNS record)
20
-
git remote add origin ssh://git@hackclub.app:33939/handle.host.tld/repo
17
+
# directly with our proxyparty server's hostname (since it's just a CNAME DNS record)
18
+
git remote add origin ssh://git@proxyparty.recaptime.dev:33939/handle.host.tld/repo
21
19
```
22
20
23
21
### Infrastructure Operations
···
34
32
> You can sign up via [Bluesky Social](https://bsky.app) or in [Tangled](https://tangled.org/signup)
35
33
> directly.
36
34
37
-
Hack Clubbers can request access by contacting Andrei Jiroh in the Slack, either
35
+
Hack Clubbers can request access for `knot.hackclub.community` by contacting Andrei Jiroh in the Slack, either
38
36
[via DMs](https://hackclub.slack.com/team/U07CAPBB9B5) or at the
39
37
[main `#recaptime-dev` Slack channel](https://hackclub.slack.com/archives/C07H1R2PW9W).
40
38