-
Notifications
You must be signed in to change notification settings - Fork 4
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
Discussion: Route Storing #458
Comments
The big question is, what kind of data do we need to store? Data That Needs to be Stored:
|
I would argue against using Firebase; it's a nice solution and would (potentially) fit our use case; however, setting up a local dev system is a pain... Also, for automated testing, it is not ideal. |
then, I propose something like "https://map.cevi.tools/recreate/UUID" which will recreate the export and create a new zip |
I would tend to use the same UUID we already use to get states and logs. This makes it much easier to generate the buttons for sharing in the frontend (and generating the QR code) |
This issue should help us track several possibilities on how to tackle route storing (#457 )
and https://github.com/mongo-express/mongo-express for viewing (on local-dev only)
The text was updated successfully, but these errors were encountered: