-
Notifications
You must be signed in to change notification settings - Fork 21
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
FLOWDB_HOST not what I expected #827
Comments
You should just be able to omit flowdb from
|
Am I missing something! You can't though right? Cos |
Shoot, no, you're right. |
Agreed @josh-gree, this is an annoying usability issue. I think the existence of |
to
Or something like that? |
I think given the typical use cases that arise in practie (which weren't quite clear when I wrote that Makefile) it's actually easier and cleaner to completely get rid of |
Describe the bug
If I run the following command to spin up flowdb with other containers;
Then the
DOCKER_FLOWDB_HOST
is not set toflowdb
as I would expect but toflowdb_testdata
as this is the default in theMakefile
. In order to specify starting a subset of services with the correctDOCKER_FLOWDB_HOST
I have to run;Specifying
flowdb
twice...And possibly allowing for somebody to do something like;Which would again lead
DOCKER_FLOWDB_HOST
being incorrect.Is there not a way of removing the
FLOWDB_SERVICES
env var completely and just finding the name of theflowdb
service fromDOCKER_SERVICES
if it exists? Also not completely clear why you ever want to have multiple versions offlowdb
at the same time!?The text was updated successfully, but these errors were encountered: