-
Notifications
You must be signed in to change notification settings - Fork 80
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
I am utterly confused by the compose instructions. #40
Comments
For approach 2, DB_ADDRESS should be: mongodb://mongoroot:password@swirl_mongodb:27017/swirl. (Assuming compose name is swirl) |
Thanks for the reply. Do you mean approach two? There is only a service called mongodb in approach two - your reference docker compose has no mongodb service. I will take this as confirmation that your docs assume a pre-setup mongodb - might be good to actually call that out in the docs. If i end up with swirl as a permanent part of my setup i can help do docs. You seem to be unaware that in a swarm stack you can call the service just by the service name - I assure you one can It still appears on the surface to to me swirl doesn't support the latest auth mechanisms correctly in mongo - but i am making a lot of un-educated guesses to get to that conclusion! Again maybe its because i didn't do something i should on mongodb? I also now realize that without a prometheus setup this is an incomplete solution. TBH the docs are very confusing about what this solution is, what is a pre-req. I think that's fine if you purely built this for yourself tho :-) - for someone who is coming from deep docker knowledge but no knowledge on what Prometheus or cadvisor are I had the wrong impression that swirl would give me out of the box stats (mostly the fault of the sites that linked me here), for example why would i need to go docker > cadvisor > prometheus when docker has native support / exporters for prometheus? tl;dr This modified version below got me up and running to see what swirl is all about with the downside there is no no auth support. (and off to learn prometheus and i guess cadvisor at the weekend)
BTW nice job on the image creation, i crawled over your dockerfile, love your keep it simple approach |
Thank you for your advice. You are right, Swirl's document should really have a pre requirements chapter. I will add this part later and provide a composite file out of the box. |
I am a little confused by the instructions and have been unable to get this working. I am unclear if i have hit an issue, didn't read something i should have (like manually creating databases and users)?
I am trying to deploy in a swarm using mongodb, i am unclear if mongodb is in the docker image or not?
I have tried both of the following:
(note i have never used mongodb before)
for approach #1 above
as such i believe there to be no mondodb server running in the container
for approach #2 above mycompose is further below, when swirl tries to connect to the mongodb it results in this if the db path ends in /swirl
if it doesn't end in /swirl i get
compose file:
note my mongo-express service connects with no issues to the database.
The text was updated successfully, but these errors were encountered: