I’m a long time airtable user interested in shifting to grist, specifically to be able to self-host on a synology nas.
I could really use an idiots guide to setting up grist core via docker in Synology DSM from scratch, as I am getting fairly lost scouting around for how to go about this. I can see SSO was an issue but that looks to be resolved, but I have never set it up before. I also don’t know what to configure during the process of creating a container - I assume I need webstation? Also never used that
Install the official Docker package from the Synology DS package center
Launch the Docker package, go to Registry and download the gristlabs/grist image (you can also do this from image by adding from a URL)
In File Station create a shared folder (I called it docker) with a sub folder called grist - I made the owner ‘docker’ (as I believe the docker service is owned by a user called docker) and gave administrators read/write access and other users read-only access.
From the Container option create a new container. If it starts, stop it immediately so you can change some settings.
Click the Edit button with the image highlighted to configure settings
These are the settings I changed
General Settings - I set Enable auto-restart
Volume Settings - I added a folder to map the container volumes to the shared volume I created at step 3 (so /docker/grist is mapped to /persist) so that documents etc persist if the container is deleted.
Then I started the container and went to the ip_of_DiskStation:8484 in the browser.
Note, my DiskStation is a DS216+II which is a pretty old machine which will only run DSM up to 7.1 - the later DiskStations are on DSM 7.2 and the package is called Container Manager for those models. Dr Frankenstein has good guides on Docker for DSM. The older guide for 7.1 is here Guide Archives - DrFrankenstein's Tech Stuff
Hey - thanks for this! I now have access to grist locally having followed your instructions.
I’m hoping to ultimately manage security for this for some contacts to be able to access my database remotely & securely. The ideal would be for people to be restricted to a domain bobsmith@examplecompany.com, with two factor authentication.
I can see there are settings and various pages relating to OIDC / SSO but I have never set anything up with either. Is this something you have set up or know how to?