-
Notifications
You must be signed in to change notification settings - Fork 17
New install from scrach authentication issues #26
Comments
Thanks for your interest! Currently, we're working quickly to get the beehive server to a production ready mode, but as of now, it's not there yet. Many of these kinds of issues will get cleaned up in the near future. Thank you for understanding. |
Hello Seanshahkarami, |
Hi Sebastian, Ah, ok. Out of curiosity, where are you all from and what groups do you all work with? Just to give you a heads up, there may be a significant simplifications which happens in terms of design and deployment, so I'm just giving you a fair warning before investing to much time in what's there now. For example, one hypothetical deployment alternative I've been putting together as an experiment outside of work is this: https://github.com/seanshahkarami/beehive-stack Something like that could make it much easier for you all to see what needs to be defined to spin up all the containers. Best, |
Sean, |
Sorry for the "radio silence" - Raj and Pete mentioned which group you're with. If you'd like to talk more actively, I'm happy to open that IRC channel or add a Slack channel if you all use that. |
We have deployed beehive-server from git using the install/beehiveInstallNew.bash script.
It had many path and silly issues we fixed, such as paths.
After it finished, we found that the RabbitMQ install has no users or maybe we have no passwords.
In short, none of the services are able to connect to MQ.
¿Is this expected?
¿Should we generate queues/users/credentials on behalf of the services?
It looks to me some part of the build failed and the users were not created.
Thank you in advance.
The text was updated successfully, but these errors were encountered: