Repository navigation
update_code in sub-directory of release_path #3002
Description
I would like to be able to checkout the repositories code to a sub-directory of the release_path.
My goal is to create a zero-downtime recipe for Grav. The flat-file cms Grav is a little bit different to most other frameworks. The repository will only contain the sub-directory user/ with custom plugins, themes, configuration and so on (see Folder Structure). My idea is to use composer create-project (see Installation) in the release_path first and then clone the content into the sub-directory user/.
Proposal:
Create update_code_path variable, which defaults to release_path, but also makes it configurable for special use-cases.
What do you think?
Activity
Schrank commentedon Mar 6, 2022
I tried that with shopware to only have it in a subdir in git and it didn’t work well. You need to change everything™️. All the build, composer install, etc. It sucked so hard, I abandoned the idea.
And now I think it doesn’t makes sense as a generic solution. It adds a lot of complexity for a small edge case very few users have.
stephan-strate commentedon Mar 6, 2022
Hmm, I don't see the problem here. Having it configurable doesn't hurt right? Because in this case the composer and build stuff needs to stick to the
release_path. Just the content needs to be in a sub-directory.How would you solve the update/deployment process of such frameworks? I'm not really into shopware, so I don't know what the requirements are there.
antonmedv commentedon Mar 6, 2022
Right now you can check out subdirectories easily https://deployer.org/docs/7.x/recipe/deploy/update_code#sub_directory
stephan-strate commentedon Mar 6, 2022
This works if you want to checkout a sub-directory of the git repository. I want to checkout the git repository inside a sub-directory in release_path.
Or we could make use of the
--prefixoption of this git archive command.