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.
Be careful when switching database type, version or credentials!
You should be careful switching database
In the case of type and version, the underlying database files between these things will likely not be compatible. In the case of credentials, these are set when the container is initially created so in order to change them you need to
lando destroy && lando start. Note that
lando destroy will delete all the data in your database.
Ignoring this warning can prevent your database from starting
services: myservice: type: mysql:5.7 portforward: false creds: user: mysql password: mysql database: database config: database: SEE BELOW # This setting only works on mysql:8.0 authentication: caching_sha2_password
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.
services: myservice: type: mysql portforward: true
services: myservice: type: mysql portforward: 3600
Setting custom credentials
You can also configure the default
password. However, it is very important to note that these things get set the FIRST TIME YOU START the service and ONLY THE FIRST TIME.
This means that if you change any of the
creds, you need to
lando destroy and then
lando start the service for the changes to take effect. This stands in contrast to the normal
lando rebuild method to change config and is a consequence of persisting the database's data directory between rebuilds.
services: myservice: type: mysql creds: user: mysql -> myuser password: mysql -> mypassword database: database -> db7
lando destroy -y && lando start
Also note that by default all
mysql services have a passwordless
root user. DO NOT ALTER THE PASSWORD OF THE ROOT USER.
Using a custom MySQL config file
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 but you can call it whatever you want such as
.lando in the example below:
./ |-- config |-- my-custom.cnf |-- .lando.yml
Landofile's mysql config
services: myservice: type: mysql config: database: config/my-custom.cnf
Your override file will get copied to
/opt/bitnami/mysql/conf/bitnami/my_custom.cnf in the database container and an include will be added to the MySQL configuration file located at
Adding tooling commands
By default a service will not do any tooling routing for you but you can add helpful
tooling: donet: service: myservice
You can then invoke them on the command line.
Lando tooling is actually pretty powerful so definitely check out the rest of its cool features.
By default a service will not do any proxy routing for you but you can add your own.
proxy: myservice: - myapp.lndo.site - something.else.local
Lando proxying is actually pretty powerful so definitely check out the rest of its cool features.