Aaron Feledy

Unstale. This seems like a useful feature request.

You're looking for build steps: https://docs.lando.dev/config/services.html#build-steps

/unstale

You're describing the default behavior of build steps. They run the first time you start the app. They do not execute during subsequent starts unless they previously failed to complete...

You can't run lando commands but this particular command actually behind the scenes runs a script that already exists inside the database container. You can execute that script with something...

@DuaelFr You _can_ do that! **.lando.yml** ``` name: myapp recipe: lamp proxy: database: - db.myapp.lndo.site:3306 ``` After a `lando rebuild`, this will tell Lando's proxy to route connections on port...

Hello @Ankit-Jaipuriar. Thank you for contributing! You can find a helpful guide for contributing to Github projects on this page: https://docs.github.com/en/get-started/quickstart/contributing-to-projects

As a workaround you could make your own alternate tooling command that does this. Something like this: ``` services: front: type: node:18 app_mount: false overrides: volumes: - "./frontend:/nuxt" tooling: ssh-front:...

Perhaps use https://github.com/jasperes/bash-yaml

Looks like you can also build the dependencies into the exe so the runtime is not needed: https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview