I just found out that Perch doesn’t recommend developing Perch supported websites in subdirectories. At present, all of my client websites that are under development are located in a clients folder in my own godaddy hosted web server.
Apparently, this is wrong. So what is the correct workflow? Should I simply purchase a dummy development domain or use something like MAMP to create a local test server? The only problem with the latter is if I want my clients to try something out before it goes live my systems are not setup to allow remote access—and for good reason.
It is interesting. If you go through the Perch forums Rachel and Drew repeatedly advise users against developing Perch sites in subdirectories. Drew even went as far as to write this article:
What makes me nervous is I need to move a soon to be completed website off of my server, which is buried three folders beneath my root to a completely different server. It sounds like I may be dealing with a mess.
Well, he does make some good points. Loading it into a sub-domain does make sense and might be better than moving it up a few levels from a sub-directory, though I’ve never had an issue (knocks on wood). I do go the MAMP Pro route and use version control. But working on a live server is working without a net. Generally I agree with him though again I’ve never had a n issue with sub-directories though maybe I should rethink that.
I also prefer developing on a remote server, preferably the one my client will be using, to ensure that everything is setup properly.
Drew’s right, there are many ways to approach this such as buying a VPS plan and configuring your own remote dev server for one. It depends on what you’re willing to do and spend to setup a proper development environment.
So here’s my dilemma. I like giving my clients the ability to proof a site remotely before it goes live, but I don’t want anyone logging into my systems. Do you think my best solution is to purchase a few development domains and hosting specifically for web development purposes?
Every time I feel like I’m getting smarter, somebody mentions something that makes me feel dumber. LOL
What is a sub-domain and how do you set that up?
On 15 Jun 2012, 3:57 am, Todd wrote:
Well, he does make some good points. Loading it into a sub-domain does make sense and might be better than moving it up a few levels from a sub-directory, though I’ve never had an issue (knocks on wood).
So here’s my dilemma. I like giving my clients the ability to proof a site remotely before it goes live, but I don’t want anyone logging into my systems. Do you think my best solution is to purchase a few development domains and hosting specifically for web development purposes?
You don’t have to buy a domain, you could, as I said, purchase a VPS server monthly plan and that would be your development platform. But that’s a more hands-on approach. But before trying that why not just try using a sub-domain of your main site instead? It could be protected from public access and you probably get an unlimited # of sub-domains as part of your hosting plan.
