Skip to content
/ lando Public

A development tool for all your projects that is fast, easy, powerful and liberating

License

Notifications You must be signed in to change notification settings

lando/lando

Repository files navigation

Lando logo

Lando

A Liberating Dev Tool For All Your Projects

The local development and DevOps tool trusted by professional developers across the galaxy.

Free yourself from the mind-forged manacles of lesser dev tools. Save time, headaches, frustration and do more real work.

learn more | what is it good for? | wait, doesn't docker compose do this?

Support Lando

Lando is and always will be FREE and OPEN SOURCE. As such it relies on generous contributions from its community to fund its development. Join our list of list of great sponsors! by contributing.

GitHub Sponsors | Patreon | OpenCollective

Documentation

Getting Started

Introduction | CLI Usage | Installation

Recipes

Backdrop | Drupal 6, 7, 8, 9, and 10 | Joomla | Lagoon | Laravel | LAMP | LEMP | MEAN | Pantheon | Platform.sh | WordPress

Services

Apache | Compose | dotnet | Elasticsearch | Go | MailHog | MariaDB | MySQL | MSSQL | nginx | Node | PHP | PhpMyAdmin | Postgres | Python | Redis | Ruby | Solr | Tomcat | Varnish

Advanced Configuration

Landofile | Recipes | Services & Build Steps | Tooling | Proxy & Nice Url Routing | Environment | Events & Automation | Experimental | Networking | Performance | Release Channels | SSH Keys | Global Config

Help, Troubleshooting & Support

Guides and Tutorials | Examples | Known Issues | Accessing Logs | GitHub Issue Queue | Slack Channel | YouTube Videos

Engage

Contribute to the Project | Join the Alliance | Events and Meetups | Blog | Follow on Twitter

Security Issues

If you have discovered a security issue with Lando, please contact the Lando Security Team directly at security@devwithlando.io. We manage security issues separately in a private repository until the issue has been resolved. Even if you're not sure if it's a security problem, please contact the security team before filing an issue, blogging, or tweeting about it.

Other Resources