zicklag
commented
3 months ago To document our current strategy for per-instance changes:
All of our configuration for both the frontend and the backend are done through environment variables, so it's very easy to configure in containers.
The instance specific stuff has so far all been in the frontend, and you can see the environment vars we use there in this file:
https://github.com/commune-os/weird/blob/b89e1be73e3e7493e2efa6474345bb9468f27967/.env.local#L14-L17
So far I'm happy with how easy this is to configure when deploying, and how easy it is to work into the development flow, but it may not be the best long term if we want to have more of an administrative interface where you can change things like the instance name.
We've already implemented some way for our deployment of Weird to be dark-default and Muni to be light-default. Similarly the members list of Weird is called 'Weird ones' 💖 whereas the equivalent page on Muni is just 'Members'.
We should do this with a few other features/fields as well, namely:
these two fields don't yet make any sense in the context of Weird.one, only Muni. Ideally we can turn these off on the Weird instance.
These different types of tweaks should be technically formalized somehow as 'Instance preferences'.