forked from lando/core
-
Notifications
You must be signed in to change notification settings - Fork 0
flos_core #8
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
Open
florianPat
wants to merge
37
commits into
3.23.25-upstream
Choose a base branch
from
flos_core
base: 3.23.25-upstream
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
flos_core #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lando directory and be able to set app mount user
…pp for v3 services
…ry to not have docker desktop warnings about the home directory volume
…ful per default ;)
containers without bash
…rt for version 3 containers and before tooling to make sure the permission setup is finished
as they default to v3 api in the event config Note that there is a difference between build steps and events: Build steps do NOT add a perm-sweep because it checks for the service version and does add a default. But I cannot change this as the "events" test fails then, as this is how it is
…o-deps flag to start containers without depending containers on exec if the full compose stack did not start yet
…fore do not copy the files over
that includes does not work there
…for events so that one can automate project setup tasks before starting the docker composition
scoped plugin and same manifest
Note that this can only happen if we use a custom core which can fall behind the upstream core/cli packages
defaults are not set otherwise and therefore no env vars are loaded
tasks from events and therefore do not repeat yourself
executing all scripts in the entrypoint didnt run all scripts anymore
initialized with an engine, so that the "docker compose config" could run and add the lando-compose and docker-compose services
installed and set to skip
…t private registries
…ter stability and performance
… for better stability and performance" This reverts commit e47222e.
…write with go modules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.