PhpFox-Site Administration-Planning for Success | PhpFox-Site Administration-Планирование успеха | |
| | |
You have an idea for a website, it is potentially a retirement plan for you and you want to do it right from the start. While we can't predict the future we can certainly be as prepared as possible for it. | The development of accounting thought | |
* One company for each task | | |
Know what your hosting company is responsible for, what your phpfox script is responsible for and what your other teams are each responsible for. As you remember a Hosting Company is an entity that hosts your website files and database, most usually they provide emailing options for you and backup features as well. They do not develop websites or change your sites colors/logo, they host it and thats their job. Reason why I bring this up is so you know what to expect from each company you deal with, even if your hosting company is very nice you should not expect them to be great at more than one thing, either they are great at hosting or great at designing. Think of it as hiring a gardener to install a new faucet. There is an entire industry for making a website look amazing, its called Web Designers. Experienced web designers have been members of the Phpfox community for many years, so you can get a good feedback about them in the forums. In fact in many outsourcing sites like GetAfreelancer or oDesk you can find a category for Phpfox jobs. | | |
* One site for each purpose | | |
You have your main website where you get traffic and you must assume at all times there is at least one customer using it. You dont want him to see an error message do you? The best way to avoid any malfunction is to develop your site in one website different than your main site, to better differentiate them we call these the Production site and the Development site. There are several ways to set up this, one is to have the development site sit on a subfolder of your production site, this has the advantage that the server configuration affecting one is also affecting the other, but it also has the disadvantage that if anything happens to the development site it could also affect the production site (like a database overload). This has the advantage of allowing cooperative development, where you do one task and other team does another (here you need to take into account access permissions, you dont want to grant the other team database access if they only will change the colors). The other way to work this is by having your development site in your local computer, if you're running windows xampp is a good alternative to quickly and painlessly setting up a local server, if you're on debian its a matter of apt-get whatever you need (script's requirements). In any way you set it up you will eventually need to move your development site to your production site, this involves a lot of details and we will publish an article just based on this. | | |
