Strategy for dev, test, and production
1) I realize that you could have 3 different linodes, but even so, I am wondering what sort of practices people use for the domain name. Could your dev and test sites be on the same linode and be accessible through different ports using the same domain name?
2) Regardless of strategy, I'm thinking that you would want to have a special indexDEV.html page, which would redirect to the index.html, that would need a password to prevent others from accessing your dev environment. Then, once you're finished with dev or test, you would leave the indexDEV.html or indexTEST.html behind, when you copy over to production. Makes sense?
Thanks for your assistance.
Joe
8 Replies
So, you might have
1.2.3.4 TestMyServer.com
1.2.3.4 ProdMyServer.com
in the /etc/host. Is that the idea?
I have my local dev box running lighttpd set to detect that subdomain and load /var/www/$subdomain so I can easily create a new folder and instantly get working on a new site without having to deal with new conf.
I use SVN to put my code on the testing & live sites. I know people say this is bad but I've done it in a smart way
I use a subdomain on each site (eg testing.domain.com) which is password protected in the lighttpd conf and which loads the /var/www/projectname/testing folder.
Once tested by the client, the live folder is updated over SVN which is almost instant.
This way I only need a single server using virtual hosts and no extra domains or dealing with hosts files. If I didn't want to run a local dev server it'd be fairly easy to do that on the live box too. With some sites I have a more complicated SVN setup but that's not really part of this discussion.
