-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add route via proxy when using Lagoon integration #6
Comments
@tobybellwood thanks for the report. Let me see if i can replicate. |
Running against latest Lando 3.0.26, steps to replicate:
name: drupal8-example-simple
recipe: lagoon
config:
flavor: drupal
build:
- composer install
proxy:
nginx:
- abcde.lndo.site
A key difference for me here is that i am getting a |
@tobybellwood, try this name: drupal8-example-simple
recipe: lagoon
config:
flavor: drupal
build:
- composer install
proxy:
nginx:
- abcde.lndo.site:8080 The |
ah, perfect - can confirm that works correctly. I'll throw a PR into the docs to help people out. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues. |
When using the Lando Lagoon integration, we should be able to add a custom route (either lndo.site or custom DNS) as per https://docs.lando.dev/guides/lando-101/lando-proxy.html
However, when trying this, even with a vanilla project (such as https://github.com/amazeeio/drupal-example-simple) the custom routes defined in the .lando.yml are not usable - but the default routes (eg mailhog) are.
I have tested alongside this with a default (non-lagoon) Lando project and it all works as expected as per documentation.
The text was updated successfully, but these errors were encountered: