New version of Robomongo released today. In this version we added support for MongoDB Authentication Mechanisms (SCRAM-SHA-1 and MONGODB-CR) and improved support for direct connection to Replica Set members.
MongoLab is awesome!
We recently learned that the team behind Robomongo, a free and open source MongoDB admin GUI, are in need of funds to keep the project going. The project, which has over 3,622 stargazers on GitHub, is a valuable free tool for the MongoDB community. We know that many of you, our customers, use and love Robomongo, so let’s try and help them!
The Robomongo team is currently fundraising on Indiegogo. To help support them, we’re announcing that MongoLab will match all donations starting now for a total of up to $15,000. Donate now and help save Robomongo!
Thank you, MongoLab!
Support for Authentication Mechanisms
This version of Robomongo allows to specify authentication mechanism. We now support two types:
Support for x.509 Certificate Authentication is planned for future versions.
If you are connecting to MongoDB 2.6 or earlier, use
MONGODB-CR mechanism, because
SCRAM-SHA-1 is only available for MongoDB 3.0 or newer.
Direct connection to Replica Set members
In previous versions of Robomongo, it wasn't possible to connect directly to Replica Set member. In this version it is possible and supported.
If you'll connect to
PRIMARY member, you will be able to write data to database. Changes will automatically propagate to your
If you'll connect to
SECONDARY member, you'll be able to view list of collections and operate in read-only mode. All required options to make this happen will be automatically set (i.e.
slaveOk for all read operations). You do not need to configure anything for this.
- Robomongo 0.9.0 RC4 for Windows (x86_64).
- Robomongo 0.9.0 RC4 for Mac OS X (x86_64)
- Robomongo 0.9.0 RC4 for Linux (x86_64)
With direct connection to Replica Set members you can do many types of database management tasks, still there is a downside of a direct connection: when topology of your replica set changes, you can find that you are not connected to
PRIMARY anymore and currently operate on
SECONDARY or vise versa.
We are very close to complete implementation of "sticky" connection to replica set members. In this case you'll be prompted for a list of servers, instead of a single one. And Robomongo, with the help of MongoDB driver, will automatically reconnect to
PRIMARY on every election of new
Expect this feature to be ready with RC5 release.
Thank you to everyone who enjoy to use Robomongo as we do!
Please, submit any found issues to our GitHub tracker.