-
Notifications
You must be signed in to change notification settings - Fork 186
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
Support write environment file such like .env, .local.env #29
Labels
Comments
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 23, 2015
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 23, 2015
REBELinBLUE#29 store,update,delete project file
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 23, 2015
REBELinBLUE#29 Clean up the project file translation
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 24, 2015
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 24, 2015
REBELinBLUE#29 store,update,delete project file
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 24, 2015
REBELinBLUE#29 Clean up the project file translation
iflamed
added a commit
to iflamed/deployer
that referenced
this issue
May 24, 2015
REBELinBLUE#29 fixed, and fix phpcs for DeployProject.php
Thanks |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know there is a way to add commend before or after each deploy step. But a large configuration file is not good to write in a command.
So support to write some files to the release path is much nice.
In order to achieve this, we need a model [StaticFile] to store the files for each project !
The text was updated successfully, but these errors were encountered: