Forum Moderators: phranque
It isn't too bad if you use localhost and relative urls. A quick glance at the address bar and there is never a question which mode is active (online vs offline). There is also the speed difference between the hd and the modem.
However; I run apache locally and it is impossible to tell whether I am online or offline by looking at the address bar. It never used to phase me because of the speed differences - until I got back to dsl. Sites can now load almost as fast online as offline, alot of times it is hard to deduce which one is active.
Time and time again over the last few weeks, I've been working on the board, leave a reply, only to later wonder where that post went too and realize I'm offline. (*splat* just did it again while making this very post - I kid you not)
When I have apache up here, I minimize it to the tray - it is so easy to forget to glance over there. I've also been doing a great deal of site dev the last couple of months that has me running apache most days during development.
I know it is a rather unique situation because most developers don't take the time to set it up. However; it cuts my dev time in half and increases the quality. It is the greatest boon to page production I've known. I could never go back.
Anyone else using a similar system to map hosts in via hosts file while running Apache?
Anytips on preventing the online/offline chaos I'm running into?
I have the same problem and don't know what the solution is other than stopping the local Apache when you intend to work on or post to your remote sites.
When a request is made through a web browser it finds the local URL and does not need to go outside the local system. If the local Apache is not running it will find the remote site without any problems.
A similar situation can occur remotely as well if you had a domain hosted with your local dialup ISP and moved it to another host provider. If the local ISP has not removed it from their nameservers you will be unable to access the new server. The domain will be found within the network that you are connected to. I have experienced this situation.
> I know it is a rather unique situation because most developers don't take the time to set it up (cuts my dev time in half and increases the quality - the great boon to page production I've known. I could never go back.)
I've been running shadow copies of my sites offline with a local Apache for a couple of years. Originally Linux was installed on my home computer to help me learn the O/S. I compiled and installed Apache and found that it worked great.
This new geeky bug had hit me and I have been unable to shake it.
A complete version of perl was compiled from source and installed, including libraries and modules. mod_perl, openssl, mod_ssl and php3 have all been compiled and installed with Apache.
My local Apache/mod_SSL server has assisted greatly in developing and hacking shopping cart scripts. Everthing can be tested and run locally using the correct path for scripts. The complete site is then uploaded to the remote server as a tar.gz file and unzipped on the server.
I have batch files setup for various configs of apache. It only takes a click to start stop it. The only hassle is exiting and restarting the browser so that it dumps the resolved ip's.
Just feeling around to see what others had setup and how to prevent the online/offline question mark. I solved a little of it by moving the modem closer to eye shot so the flickering lights will either wake me up, or drive me insane (huge green leds).
