It looks like you are connecting to a MongoDB Atlas instance. I’ve found that MongoDB Atlas tries to enforce every best practice on you from the beginning (e.g. defaulting to replica sets, starting out with no IP addresses whitelisted, etc.), which in turn makes everything very complicated to get up and running. This is in contrast to mlab which is pretty simple to get started with (I find I can get started with mlab in a fraction of the time as with MongoDB Atlas). The only problem with mlab is that it is being merged into Atlas in the near future, making Atlas the stronger long-term solution.
Anyway, I am working on a set of changes to FireWorks right now that will allow you to connect with a connection URI (e.g., in your example this would be mongodb+srv://cluster0-b05rv.mongodb.net/test). They should hopefully be fully ready in a week or less (I already have some draft commits, just trying to test them properly with a MongoDB Atlas configuration). I will update you when ready.
On Thu, Apr 4, 2019 at 3:21 PM ‘Sim’ via fireworkflows [email protected] wrote:
I have installed FW (connection to the remote test-server works) and set up a cloud mongodb atlas instance.
Now I wan to point FW to my mongodb. So I created a FW_config.yaml and set my os.env.var for FW_CONFIG_FILE to point to this file.
When I call lpad version I get the ValueError: Invalid FW_config file has unknown parameter: host.
I am not sure which format to use (the doc seems to skip this step): (for mongo shell)
or this (from CLI tools info)
You received this message because you are subscribed to the Google Groups “fireworkflows” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fireworkflows.
For more options, visit https://groups.google.com/d/optout.