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
Changing the paths where mosparo stores the generated files (for example, the prepared CSS files for the frontend) can be interesting for different use cases. In a multi-node setup, for example, it can be interesting to store the files in a different, synchronized location but without synchronizing the whole mosparo code.
For this, we add three (or more) different environment variables with which it is possible to define an alternative location to load and store the configuration file, the CSS files for the frontend, the data directory to store the GeoIP2 database, import files, and more.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Idea
Changing the paths where mosparo stores the generated files (for example, the prepared CSS files for the frontend) can be interesting for different use cases. In a multi-node setup, for example, it can be interesting to store the files in a different, synchronized location but without synchronizing the whole mosparo code.
For this, we add three (or more) different environment variables with which it is possible to define an alternative location to load and store the configuration file, the CSS files for the frontend, the
data
directory to store the GeoIP2 database, import files, and more.Inspired by
Discussion
Beta Was this translation helpful? Give feedback.
All reactions