-
Notifications
You must be signed in to change notification settings - Fork 5
Have a mocked up environment for developing locally #190
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
Conversation
You need to use your fake user - [email protected] password :) |
@leihelondon as discussed this morning - we'd need a ticket for setting up a dummy storage and transcription as it's not implemented as part of the emulators yet... but it does look like it's just around the corner: firebase/firebase-tools#1738 We might either: wait it out, or maybe try out the beta version 🗡️
The local environment will try and upload a file, but will fail like so: |
As discussed, moving this to backlog until we have a solution for emulating storage. |
Is your Pull Request request related to another issue in this repository ?
Having a look over the Firebase docs, it looks like many more features are supported for emulators!
Which means a lot of the scripts and dependencies to run servers in parallel can now be simplified.
I have been working from an older version of docs when speaking about their testing strategy - they encourage to use emulators over
serve
. See https://firebase.google.com/docs/hosting/test-preview-deploy and https://medium.com/firebase-developers/setting-up-a-fully-functional-database-in-firebase-emulator-b0199fff0252Describe what the PR does
npm run start
should now start the emulator, use the emulated DB and have a hot-reloading local version.localhost:5000/*
as well, in case you want to run the build version using the emulator.State whether the PR is ready for review or whether it needs extra work
Ready
Additional context