Q1.How to say quick and growth chronicle of a website?
I am perplexing to build a website from scratch, and we am graceful new to this. we was wondering how we can keep a quick chronicle published while we am offer developing.
I was pondering of carrying twin folders on my server /Dev and /Stable and afterwards sourroundings a Directory Index in a .htaccess record to indicate to a Stable version.
Is this an effective proceed of doing this?
Answer:
The best use for this assign it to use opposite domains for this, as Pekka points out. You could have www.website.com for a wholly so called "live" chronicle and e.g. test.website.com or dev.website.com or staging.website.com – with evidence word – for development.
But that competence be a financial issue, so one thing we can always do is to run a finish website as a internal chronicle on your mechanism – e.g. controlling XAMPP in box you're not smooth with sql / web / ftp / mail server setup.
In any box it's a good personal ability alleviation if we learn how to setup and run some-more or reduction a same sourroundings your website is controlling underneath on your internal machine!
Furthermore we competence wish to start controlling a versioning program like e.g. Subversion or even some-more worldly git. That proceed we can offer enhance/develop your formula and though do hotfixes on your controlling chronicle but carrying to say 2 opposite record trees.
Q2.PHP: Detect and arrangement “Server overloaded” message
I have beheld a few websites such as hypem.com arrangement a "You didnt get served" blunder summary when a site is bustling rather than only permitting people wait, time out or refresh; aggravating what is substantially a server bucket issue.
We are too hallowed to slight your request. Please click "back" in your browser and try what we were doing again.
How is this achieved before a server becomes overloaded? It sounds like a unequivocally neat proceed to control user outlook if a site happens to get overloaded while also giving a site time to recover.
Answer:
This competence be to do with a database tie timing out, though that assumes that your server has a bigger DB bucket than CPU bucket when times get tough. If this is a case, we can make your DB connector arrangement a summary if no tie happens for 1 second.
You could also use a discerning query to a logs list to find out how many hits/second there are and automatically not respond to any some-more after a certain indicate in method to safety QOS for a others. In this case, we would have to set that turn manually, formed on server logs. An choice slight can be seen here in a Drupal stifle module.
Another choice would be to use a Apache station page to get information on how many child processes are giveaway and to stifle id there are zero left as per @giltotherescue's answer to this question.