I have been meaning to use Grist for an educational org I volunteer for - mainly to manage student data. We would definitely self-host, and it is great that there is already a Class Enrollment template. Your self-hosting docs [1] seem pretty straightforward. However,
* I am annoyed that the the app requires providing inputs through command line args or environment variables rather than a fixed config file that I can store in git.
* Some directions on creating a service that starts the app on server restart etc would be good.
Thank you. I've been struggling with a good story for configuration. I'm not entirely satisfied either with using environment variables for everything.
Using Docker, you can just put your env-vars in a file and execute Docker with --env-file specifying where your configuration is, which is what I currently do, but perhaps a .env file would be more standard and comfortable.
Let me put it this way. Your app has wide possible usage, including a lot of casual usages, by relatively non-technical users. Like small businesses or clubs etc, as your templates show. Spreadsheets run the world, and grist is turbo spreadsheets.
If you want those people to use your software, you should make it as easy as possible to install it. Think of a tech-minded teenager helping their dad set up grist to track inventory for their corner store. How can you help them install the software in a couple of hours?
Comments
I have been meaning to use Grist for an educational org I volunteer for - mainly to manage student data. We would definitely self-host, and it is great that there is already a Class Enrollment template. Your self-hosting docs [1] seem pretty straightforward. However,
* I am annoyed that the the app requires providing inputs through command line args or environment variables rather than a fixed config file that I can store in git. * Some directions on creating a service that starts the app on server restart etc would be good.
[1] https://support.getgrist.com/self-managed/
Thank you. I've been struggling with a good story for configuration. I'm not entirely satisfied either with using environment variables for everything.
Using Docker, you can just put your env-vars in a file and execute Docker with --env-file specifying where your configuration is, which is what I currently do, but perhaps a .env file would be more standard and comfortable.
Let me put it this way. Your app has wide possible usage, including a lot of casual usages, by relatively non-technical users. Like small businesses or clubs etc, as your templates show. Spreadsheets run the world, and grist is turbo spreadsheets.
If you want those people to use your software, you should make it as easy as possible to install it. Think of a tech-minded teenager helping their dad set up grist to track inventory for their corner store. How can you help them install the software in a couple of hours?