Rob Ballantyne

Latest builds now support setting `SUPERVISOR_NO_AUTOSTART="syncthing,jupyter"` etc - names pulled from the `supervisor-{service name}.sh` scripts

You may well be right. Unfortunately I don't have access to an AMD card so I'm building blind for the target. The default provisioning script is just an example so...

I have added a ROCm provisioning script to the config directory. Currently all it does is remove bitsandbytes but I'll add the AMD version at build time asap. Sorry for...

Sorry for the late reply. You need to set Authorization headers https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization Currently only Basic is supported but the next update will also permit Bearer

Both basic and bearer supported

Thanks @gymdreams8 I'll change it. The provisioning script is user replaceable and I'm happy to be guided as to what should be default, and this makes perfect sense.

Quick thought on this: Maybe something like `apply-config.sh https://some.site/some-config-slug` Executes ``` wget -O custom.sh "${1}" source custom.sh ``` You could host a UI to generate and host a bash script...

I can look to do something like that. I'm re-working the service portal now, so that links, logs and service start/stop controls all appear in a unified interface so there...

I'll add it, but I have quite a few to do. I have been asked for invoke and sd.next plus I am spending quite a lot of time making sure...

You'll need the Nvidia container toolkit installed on the VM for the GPU to be available to docker. The compose file will also need the Nvidia devices section uncommentiing https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html...