Add support for Flow in a subfolder #94
Merged
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
Member
Author
|
Best used with flownative/docker-beach-php#20 😎 |
kdambekalns
force-pushed
the
feature/flow-in-subfolder
branch
from
bbbf1f1 to
9b1dff7
Compare
With this change a set FLOW_ROOT_PATH in the environment variables will be respected by Local Beach. This affects the commands `logs` and inidrectly `resource-download` and `resource-upload` as well.
The sandbox was used only to read the project name – but the config was written to the current directory anyway. Now the current working is used to define the project name, the check for Flow installation is no longer done at this point.
This allows to have a project folder where the Flow distribution root
is in a sub-folder.
`beach init --flow-path some/folder` can be used to initialize a setup
where the "Flow project root" is in `some/folder`. This will now
set the (new) environment variables like this:
BEACH_FLOW_ROOTPATH= some/folder
BEACH_APPLICATION_PATH=/application/some/folder
kdambekalns
force-pushed
the
feature/flow-in-subfolder
branch
from
9b1dff7 to
8ef2055
Compare
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.
This allows to have a project folder where the Flow distribution root is in a sub-folder.
beach init --flow-path some/foldercan be used to initialize a setup where the "Flow project root" is insome/folder. This will now set the (new) environment variables like this:This can be used for projects where a Flow or Neos distribution is part of a larger codebase and the root is not reserved for Flow or Neos.