Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store config and statuses in Firebase #125

Closed
eXistenZNL opened this issue Mar 24, 2019 · 0 comments · Fixed by #126
Closed

Store config and statuses in Firebase #125

eXistenZNL opened this issue Mar 24, 2019 · 0 comments · Fixed by #126
Labels

Comments

@eXistenZNL
Copy link
Collaborator

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.

@eXistenZNL eXistenZNL changed the title Optionally store config and statuses in Firebase instead of locally Store config and statuses in Firebase Mar 24, 2019
rick-nu pushed a commit that referenced this issue May 10, 2019
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant