Lando is a free, open source and cross-platform local development environment tool built on Docker container technology. It is the successor project to Kalabox.
- Installation
- Getting Started
- Configuration
- Recipes
- Services
- Tooling Options
- CLI reference
- Contributing
- API
- Troubleshooting and Support
- Examples
Or browse all our docs.
Lando seeks to provide stored-in-version-control, single-config-file and per-app configuration to manage the dependencies a project needs to run and developers need to develop. It aims to be easy to use and fast.
With Lando you can...
- Easily mimic your production environment locally.
- Setup, develop, pull and deploy your sites super fast.
- Standardize your teams dev environments and tools on OSX, Windows and Linux.
- Easily customize or extend tooling, deployment options and basically any other functionality.
- Free yourself from the tyranny of inferior local development products.
A developer should be able to get a running site and the tools needed to develop that site with a single, short config file called .lando.yml
that lives in the root directory of your project and a few lando
commands.
git clone myproject.git
cd myproject
lando start
cd /path/to/my/local/code
lando init appname
land start
mkdir -p mysite
cd mysite
lando init mysite pantheon | lando init mysite github
lando start
You can also easily configure a lando.yml
recipe
name: myproject
recipe: lamp
config:
php: '7.1'
webroot: www
database: postgres:9.6
config:
php: config/php.ini
or go totally nuts and scaffold out a custom stack
name: myproject
recipe: lamp
config:
php: '7.1'
webroot: www
database: postgres:9.6
config:
php: config/php.ini
services:
node:
type: node:6.10
globals:
grunt-cli: "latest"
cache:
type: memcached:1.4
mem: 128
search:
type: solr:5.5
core: hard
tooling:
node:
service: node
npm:
service: node
grunt:
service: node
Lando is seeking to eventually merge into and then replace the Kalabox project. This means that eventually Lando will have all the great features you've come to love in the Kalabox project. That said the primary high level goals for this transition are to
- Provide a more reliable and robust underlying product
- Replace MAMP and other local dev stacks
- Reduce the complexity of building out complicated apps a la Pantheon
- Implement a simple per-app configuration file that can be stored in version control
- Provide mechanisms for packaging in development tools and build steps along with services
There are various features that need to be implemented to achieve the above.
Transition the core frameworkProvide a services layer on top of docker composeProvide a build and tooling layerProvide additional core services and toolsProvide a recipes layer on top of servicesProvide handling of upstream git remotes (lando init command)- Provide a push/pull layer on top of the tooling layer
Replicate Pantheon environment- Integrate with Pantheon
- Build GUI