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
It would be very nice if we could store the config and statuses of CIMonitor in an external tool like Firebase, so we do can keep state when running the Docker container.
Why
This helps us keep state when updating the docker container.
The text was updated successfully, but these errors were encountered:
* Add configurable storage for statuses and config, and add a Firebase backend (#125)
* Update Cypress to v3.2.0
* Separate the config loader from the actual config
* Codestyle fixes
* Add docs for Firebase
* Rename loader to configLoader, optimize the object creation when loading from Firebase, rename an environment variable
* Make the module client work correctly
* Streamline loading the config when starting the application, improve the config structure when loading from Firebase
* Add Jest tests for the Filesystem config loader
* Fix link to the Firebase page in the CIMonitor page
* Add the test for the Firebase config loader
* Various small suggested improvements
* Fix the Jest target in the Makefile
* Make use of the recommended sharable eslint configuration for jest
* Remove trailing comma from .eslintrc and add all Jest files to the .dockerignore for both containers.
* Remove extra dev-server make target that was used for developing the Firebase backend
What
It would be very nice if we could store the config and statuses of CIMonitor in an external tool like Firebase, so we do can keep state when running the Docker container.
Why
This helps us keep state when updating the docker container.
The text was updated successfully, but these errors were encountered: