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
Getting the emulator into a docker container seems to be the easy part. In doing this I see a few potentials with the tight coupling the emulator code has on the manifest.json.
To correct that I see a few options.
Copy manifest into app directory / change config to reference local path to /app/manifest.json
Mount path to manifest on local file system when running container & change config to reference that mount path in container
Abstract emulator code to not be dependent on the manifest and duplicate manifest bits in emulator
config.
Some combination of 3 and 2/1.
If I've missed a potential scenario, please chime in.
I'll create the Dockerfile and update the readme with directions for points 1 and 2 above. If we want to take a different direction in the future, it can be decided then.
With the emulator in a container, it would be easy to use for integration testing during CI processes
The text was updated successfully, but these errors were encountered: