My apologies. I had looked at that and completely missed it.
Sean
Jamis Buck wrote:
It's actually been on the upgrade FAQ for awhile :)
http://www.capify.org/upgrade/faq
- Jamis
On 7/18/07, Thibaut Barrère [EMAIL PROTECTED] wrote:
I had exactly the same question; thanks! Should it
Andy,
I'm investigating even as we speak. I was set up with an account that
exhibited the problem, and I was finally able to duplicate the problem
there, which has helped. I'll post more as soon as I have more info.
- Jamis
On 7/19/07, Andrew Beacock [EMAIL PROTECTED] wrote:
Jamis,
Have
Just had an idea flash, that might already exist and would be way
cool if it did.
cap edit FILE=/etc/hosts ROLES=web
(1) check that the file is identical on all hosts
(2) get and open the file with $EDITOR
(3) upload the altered file
I don't know about you, but that gives me goosebumps :)
On Jul 19, 2007, at 6:57 PM, Tim Carey-Smith wrote:
* Jamis Buck [EMAIL PROTECTED] [2007-07-19 15:41:42 -0600]:
Neat idea, Mat. I don't know of anything that currently does that,
but
if you find a nice way to implement it, I'd certainly consider adding
it to cap. Bonus points if it
You would use svn switch.
http://svnbook.red-bean.com/en/1.1/ch04s05.html
On 7/19/07, Nick [EMAIL PROTECTED] wrote:
Dear all,
I changed my production server from a local IP 192.168.1.4 to a domain
name. I deploy with capistrano and the first deployment works.
However, the svn commit
* Nick [EMAIL PROTECTED] [2007-07-20 01:43:58 -]:
I changed my production server from a local IP 192.168.1.4 to a domain
name. I deploy with capistrano and the first deployment works.
However, the svn commit command still wants to connect to my old IP
and not my domain even though I
