You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally I have a two server setup with both acting as front ends both syncing with each other to stay current with apps and bookmarks. The way I am doing this right now is super jank. Some of the complexity has to do with flame running in a docker container for convenience (ik, ik).
I think it would be super nice to have at some level support for a configuration as such.
Easiest way I can see to support it is to make the db.sqlite file in its own folder so that that folder can be mounted as a network share without changing anything else about the container configuration.
While this works, it does limit each instance to use the same weather data as its not tagged with location in the db.
For that solution I would say that the db_backups folder should not be in the share, just in case.
About sharing the config.json as well, I would say that that would probably not be practical when differentiating the servers at a glance.
I might make a fork and work out that stuff, but I do want just some thoughts on that idea and if anyone else would like it.
The text was updated successfully, but these errors were encountered:
Title's not great.
Personally I have a two server setup with both acting as front ends both syncing with each other to stay current with apps and bookmarks. The way I am doing this right now is super jank. Some of the complexity has to do with flame running in a docker container for convenience (ik, ik).
I think it would be super nice to have at some level support for a configuration as such.
Easiest way I can see to support it is to make the db.sqlite file in its own folder so that that folder can be mounted as a network share without changing anything else about the container configuration.
While this works, it does limit each instance to use the same weather data as its not tagged with location in the db.
For that solution I would say that the db_backups folder should not be in the share, just in case.
About sharing the config.json as well, I would say that that would probably not be practical when differentiating the servers at a glance.
I might make a fork and work out that stuff, but I do want just some thoughts on that idea and if anyone else would like it.
The text was updated successfully, but these errors were encountered: