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.

Sign up for GitHub

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

Jump to bottom

Strategy for Development with Containerised FlowForge #51

Open
Pezmc opened this issue Feb 10, 2023 · 0 comments
Open

Strategy for Development with Containerised FlowForge #51

Pezmc opened this issue Feb 10, 2023 · 0 comments
Labels
task A piece of work that isn't necessarily tied to a specific Epic or Story.

Comments

@Pezmc
Copy link
Contributor

Pezmc commented Feb 10, 2023

Story

No response

Description

I was trying to get a copy of FlowForge with real Node-Red running within Docker locally working and supporting modifications to the codebase.

However, @hardillb and I ran into blockers around newly created projects trying to speak to the wrong instance of forge (when running forge from command line and all other containers within docker).

Having a way to run Dockerized FlowForge from a location where the files can also be modified (or a hybrid setup) would be valuable for more "real world" development locally, particularly when testing interactions with NodeRed and FlowForge e.g. the Team Library.
@Pezmc Pezmc added the task A piece of work that isn't necessarily tied to a specific Epic or Story. label Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
☁️ Product Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pezmc