core/docker/ at a3f005f8c83d2c0753e51b7a7400089269f41448 · alice.pds.demo.boltless.dev/core · Tangled

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / docker

1 folder 2 files

at a3f005f8c83d2c0753e51b7a7400089269f41448

hanna docker: update to unified binary deployment 1y ago

docker: update to unified binary deployment

1 year ago

docker: update to unified binary deployment

1 year ago

docker-compose.yml

docker: make docker-compose serve https and fix permissions This fixes two issues I had when deploying the eeg.cl.cam.ac.uk knot: 1) The permissions on the volumes are currently set at build time, which means that when a fresh volume is mounted it has the wrong permissions. This fixes it to run the chmods on the volumes dynamically at entrypoint time, which lets a fresh volume work with a knotserver. The error before was: ``` knot-1 | time=2025-05-04T13:58:36.054Z level=ERROR msg="failed to setup db" error="unable to open database file: no such file or directory" ``` 2) It's a little odd for the default setup to expose 5555 and insecure http to the Internet, given that the appview will try to connect to the knot over https. This adds a standalone Caddy server as the default and removes port 5555 from being directly explosed. A more advanced user with an existing proxy can easily remove this from the compose file and hook in their own. The only remaining footgun my users have encountered is that of port 2222 being the default. Almost all the users have forgotten to add the `port 2222` directive in their ssh_config, and the _host_ sshd rejects them. In my local setup, I've swapped the host and knot ports around so that the knot runs on 2222, but a really elegant solution would be for some sort of ssh proxy on the host ssh to redirect the `git` user to the knotserver sshd. I haven't done that yet though!

1 year ago