tangled.org / knot-docker
Community maintained Docker config for the knot server
101
fork

Configure Feed

Select the types of activity you want to include in your feed.

readme: update docker-compose usage #3

open opened by
codeka.io targeting main from codeka.io/knot-docker: main

This updates the docker-compose section with more usage instructions.

When I tried to setup my own knot using the provided docker-compose, I had to update the ownership of the directories to match the ones in the docker container, so I included this small instructions in the provided script.

Also the caddy profile was not documented, so I added a section about it.

I also added a small "Pushing code using SSH" section, with the required configuration on the client machines (to connect to the port exposed by the container)

Labels

None yet.

Participants 1
AT URI
at://did:plc:a27wdjlmq3ebx4v5f2jpzvsk/sh.tangled.repo.pull/3mkvhaysfzf22
+6 -5
Interdiff #1 → #2
+6 -5
readme.md
··· 69 69 chown -R 1000:1000 keys repositories server 70 70 ``` 71 71 72 - Replace the `1000:1000` ids if you build your docker image with different ids. 72 + Replace the `1000:1000` ids if you built your docker image with different ids. 73 73 74 74 Then start the knot container using: 75 75 ··· 80 80 docker compose up -d 81 81 ``` 82 82 83 - If you also want to setup a reverse proxy with TLS auth, use the `caddy` profile of the compose: 83 + If you also want to setup a reverse proxy with TLS termination, use the `caddy` profile of the in the compose file: 84 84 85 85 ```sh 86 86 docker compose --profile caddy up -d 87 87 ``` 88 88 89 - The knot server will be exposed on the given port. 89 + The knot server will then be exposed on the given port. 90 90 91 91 ## Pushing code using SSH 92 92 ··· 102 102 - "2222:22" 103 103 ``` 104 104 105 - Thus, when trying to push code to your knot, say `git@knot.example.com/someRepo`, Git will use port 22 by default (which will resolve to your docker host's SSH daemon). 106 - Configure ssh to use the port exposed by your container in `~/.ssh/config`: 105 + By default, when you push code to a remote, such as `git@knot.example.com/someRepo`, Git will use port 22, which will resolve to your docker host's SSH daemon, not the container. 106 + 107 + To connect to the knot container over Git with SSH, configure your SSH client to use the port exposed by the container in `~/.ssh/config`. 107 108 108 109 ``` 109 110 Host knot.example.com

History

4 rounds 0 comments
sign up or login to add to the discussion
codeka.io submitted #3
diff interdiff
1 commit
expand
3534bd15
readme: update docker-compose usage
no conflicts, ready to merge
expand 0 comments
codeka.io submitted #2
diff
1 commit
expand
77911f4b
readme: update docker-compose usage
expand 0 comments
codeka.io submitted #1
diff interdiff
1 commit
expand
14714dcb
readme: update docker-compose usage
expand 0 comments
codeka.io submitted #0
diff
1 commit
expand
4a0b023a
readme: update docker-compose usage
expand 0 comments