search

pocketarc / git-deploy-php

git-deploy-php is a simple php-based tool that deploys your Git repositories to FTP/SFTP servers, and keeps them updated automatically.
http://brunodebarros.github.io/git-deploy-php
291 stars 45 forks source link

Nothing Responding #45

Closed ajtroxell closed 9 years ago

ajtroxell commented 9 years ago

On my local machine, running php git-deploy seems to process momentarily and then simply prompts me as if i'd done nothing at all. 2014-10-20 21_20_47

pocketarc commented 9 years ago

Not sure what the problem could be here, but I haven't run git-deploy on Windows in years, so it may have something to do with that. Do you have any PHP experience at all? Can you die() along the way and see if you can spot where the script is stopping?

pocketarc commented 9 years ago

Actually, another thing is: Do you have a deploy.ini file? Does that file have valid FTP/SFTP servers for you to deploy to? I think that if you don't have any servers (or if all the servers are skip = true), it doesn't output anything at all. Can you double-check this?

ajtroxell commented 9 years ago

I can die sure, but can I print to the console when doing so, so I can spot the line? Deploy.ini is configured properly, servers are not set to skip. PHPloy works for me, which is a fork of your project, but i'd much prefer the simplicity you have here.

[removed screenshot for privacy]

pocketarc commented 9 years ago

Don't forget to change your password now that you've broadcasted here on Github. I've removed the screenshot.

I've noticed that you have skip = true on your server, that means the server is skipped. You said they're set not to skip. In that case, they should be skip = false. Can you do this and see if it makes a difference?

ajtroxell commented 9 years ago

My mistake. I originally had skip set to false, then set it to true to see if I got any results. It was then that I send the screenshot instead of when I had it to false. However, this morning I tried things out, and for some reason all of a sudden it is working. The only thing different is that now I have added in the text [example] before my credentials. I now have it successfully running using an ini file each for staging and production environments. Thanks for your help!

pocketarc commented 9 years ago

Yes, that [example] is necessary; it's the title of your server. So you could, for example, have [production], [staging], and [development] servers.

pocketarc commented 9 years ago

I'm glad things are working for you now!

ajtroxell commented 9 years ago

Want to make sure I get this right. To deploy to more than one server independently,I need multiple deploy.ini files (staging.ini and production.ini), but if I want to deploy to multiple servers at once, I would make multiple servers ([staging] and [production]) within the same deploy.ini?

pocketarc commented 9 years ago

That is exactly right, yes.