'Safe'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
I just got one, too.
January 9, 2003, 4:10 pm Jesse[8]: ERROR [2] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) line 72 of file /home/buffist/public_html/classes/giles.php
January 9, 2003, 4:10 pm Jesse[8]: ERROR [2] MySQL Connection Failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) line 72 of file /home/buffist/public_html/classes/giles.php
Okay, seriously stupid question, but I really don't know what to do here. I need to sign in again as my Evil Self for Sang Sacre. Do I have to start a new account, or what?
you want the name "evil self" only for the sang sacre thread?
Penny, insent to profile addy.
KNUT!!
Thank you, David!
Yes, I want an assumed name, but only for Sang Sacre. It's not my fault, really. Some evil wizard cast a mirror spell
My head is exploding. Bad CVS! Bad CVS!
Well, okay, what's bugging me is methodology, not the application.
We need:
Now, CVS does the first, and we already have the second. I'm not having any joy with how to combine them both in a safe and lovely manner.
Ideas from those with expertise?
Because just having folks FTP stuff up isn't working, with the stepping on, and vanilla CVS isn't allowing for testing.
If the problem is people overwriting changes on the test server, you could check a file into CVS that contains a list of people in line to use the test server. The top person on the list can do what they want with the server. When they're done, they take themselves off the list.
That, at least, will keep accidental stepping on.
I don't imagine two people can share the test server at the same time, at least not reliably.
I don't imagine two people can share the test server at the same time, at least not reliably.
There must be a way. I don't say that because I can even halfway think of one, but because someone must be doing, it, right? A test site per coder is way too many.
I'm hoping I can get a fake phoenix running on my Mac. That might help.
The other way would be to break up the Phoenix source into modules that we're convinced are independant. Then folks can test the modules simultaneously.
But otherwise, no, I don't think two people can be modifying and testing the same program at the same time on the same machine and not go insane.