Skip to content
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

Can you specify staging/production servers in the one deploy.ini file? #1

Closed
SimonEast opened this issue Feb 11, 2014 · 4 comments
Closed
Labels

Comments

@SimonEast
Copy link
Contributor

This looks awesome, just the kinda thing I need. Gonna attempt to try it out tomorrow, but just wondered if there might be a way to specify separate settings for staging/production servers, so you could do something like

phploy production
or
phploy staging

I realise that this was probably intended for a workflow where you have separate Git branches for staging/production in which case a different deploy.ini file for each. I sometimes do that, but for simpler projects with mostly linear development, it's nice to deploy to staging, get approval from the client and then run 1 command to get that on production.

I might even see if I can build that feature myself.... hmmm...

(Also, from a quick glance, shouldn't the deploy.ini file be in $files_to_ignore? It should also ignore the entire .git folder.)

Thanks for sharing this.

Simon.

@banago
Copy link
Owner

banago commented Feb 11, 2014

Hi @SimonEast,

Thanks for the feedback. The production/staging functionality is on the making - it's coming.

As for ignoring deploy.ini, it's done in the parseCredentials method, even though it's not very obvious. It's like that in case you want to provide another name for the deploy.ini file.

I'd love to hear more after you give it a try.

Thanks,,
Baki

@banago
Copy link
Owner

banago commented Feb 11, 2014

Hey @SimonEast,

This feature is now in place. :)

@SimonEast
Copy link
Contributor Author

Yeah, it's fantastic, love it! 👍 And thanks so much for getting that feature in so quick, woo! :-)

It worked great on the 4 repos I tested it with this morning. There are a few quirks/gotchas with getting it working smoothly on Windows (ie. ANSI colors and UTF-8 chars), but I might write up some of those steps and add it to your readme when I get some time.

The next feature I'm wondering about (and can create a separate issue if needed), is rolling back a commit or two... If you reset your HEAD back and then ran the deploy again, is it possible for the script to detect the changes deploy the changed files (kind of in reverse?).

With that in place, I could potentially stop paying for Beanstalk to do FTP deployments for me. :-D

@banago
Copy link
Owner

banago commented Feb 12, 2014

Hi @SimonEast,

I created an issue for the rollbacks. I will write a comment there where I will ask for your opinion on the HEAD reset.

In the meanwhile, if you could share those tips about the Windows quirks, that would be great. I want windows users to have a seamless experience with the script too.

banago pushed a commit that referenced this issue Sep 30, 2016
banago pushed a commit that referenced this issue Dec 7, 2016
banago pushed a commit that referenced this issue Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants