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
Support backend-only development mode (#1327) #1339
Support backend-only development mode (#1327) #1339
Conversation
@RobertIndie I had a look at the backend-only configuration and think this setup has never worked as the UI could not properly connect to the locally running backend. I also had some problems when trying to create adapters and pipelines with the extensions service running in Docker as more environment variables need to be set in order to make sure the extensions get the right broker connection settings from the backend. So I removed the Sorry for the long explanation - can you please give it a try? I hope this workaround works ;-) |
@dominikriemer Hi, Thanks for your PR. The UI works now! But when I start
Do I miss something? Semes the target host is not specified. How can I set the host? |
Great! |
Hi @dominikriemer |
- couchdb | ||
volumes: | ||
- files:/spImages | ||
# Set SP_HOST to an IP or hostname that can be resolved from the Docker container and local-running backend |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we cleanup this comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the comment and will add the info to the documentation, thanks!
Purpose
Modify the
backend
environment which allows to run StreamPipes for backend-only development purposes.Added a new service definition
ui-custom-conf
which adds a volume mapping from a custom Nginxdefault.conf
file where the upstream of the reverse proxy can be set to a hostname that links to the locally running backend.Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no