···11-# knot-docker
11+# Knot Docker
22+33+> **IMPORTANT**
44+> This is a community maintained repository, support is not guaranteed.
55+66+Docker container and compose setup to run a [Tangled](https://tangled.sh) knot and host your own data.
77+88+## Simple Setup
99+1010+If you want an easy way to spin up a knot, you can simply run the following
1111+with docker installed:
21233-This is a community maintained Docker setup for hosting your own knot
44-server.
1313+```console
1414+$ docker compose up -d
1515+```
1616+1717+This will setup the knot server, as well as caddy to expose the front-end.
1818+1919+## Bring Your Own Setup
2020+2121+If you have your own compose setup already, you will just need point your web
2222+server to the knot's HTTP port (namely `5555`), you can do this with docker by
2323+setting another container to `depends_on` it and then pointing it to the name
2424+of the container with the port. For example, with a very basic caddy webserver
2525+container:
2626+2727+```
2828+caddy reverse-proxy --from ${KNOT_SERVER_HOSTNAME} --to knot:5555
2929+```
3030+3131+This will for example point caddy to the port on the knot container.
3232+