Here are the configuration options, set to the default values, for this service. If you are unsure about where this goes or what this means, we highly recommend scanning the services documentation to get a good handle on how the magicks work.

Also note that options, in addition to the build steps and overrides that are available to every service, are shown below:

    type: mongo:4.0
    portforward: false
      database: SEE BELOW

Be careful when switching database version!

You should be careful switching database version because the underlying database will not be compatible unless you follow these steps to upgrade it:

If you have a current project with 4.2 that you wish to upgrade to 5.0, you need to upgrade to 4.4 first (change the version, run lando rebuild) and do the tiny step described here:

Run the setFeatureCompatibilityVersion command against the admin database: db.adminCommand( { setFeatureCompatibilityVersion: "4.4" } )

Before you update the mongodb version to 5.0 and repeat the above step.

You can also use mongodump to create a backup of your database, delete the mongo instance, recreate it on a new version and use mongorestore to populate the database again.

Ignoring this warning can prevent your database from starting

Port forwarding

portforward will allow you to access this service externally by assigning a port directly on your host's localhost. Note that portforward can be set to either true or a specific port but we highly recommend you set it to true unless you have pretty good knowledge of how port assignment works or you have a very compelling reason for needing a locked down port.

portforward: true will prevent inevitable port collisions and provide greater reliability and stability across Lando apps. That said, one downside of portforward: true is that Docker will assign a different port every time you restart your application. You can read more about accessing services externally over here.



    type: mongo
    portforward: true

Not recommended

    type: mongo
    portforward: 27018

Using a custom MongoDB config file

You may need to override our default mongo configopen in new window with your own custom mongo configopen in new window.

If you do this, you must use a file that exists inside your application and express it relative to your project root as shown below:

A hypothetical project

Note that you can put your configuration files anywhere inside your application directory. We use a config directory in the below example but you can call it whatever you want such as .lando.

|-- config
   |-- custom.conf
|-- .lando.yml

Landofile's mongo config

    type: mongo
      database: config/custom.conf

Getting information

You can get connection and credential information about your mongo instance by running lando info. It may also be worth checking out our accessing services externally guide.