Don't develop Perch sites in subfolders?
This is the archived Perch forum. Please post new requests to the new Perch forum
I've been reading through several posts that recommend that users don't develop Perch websites in subfolders. Isn't that a little unrealistic?
I mean most design companies I know of will develop client sites on their own web servers, within a client or development subdirectory. But, perhaps I'm missing something. Please walk me through the workflow you are suggesting?
I just found this article that Drew wrote, which is very good.
So here's my dilemma. Most of my clients already have a website, so I'd rather not use their server for fear of screwing something up. 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. Having said all of that is my best solution to purchase a few development domains and hosting? c
After researching this for a few hours I think MAMP PRO is my best choice, which I think I've seen Rachel use in some of her tutorials. How hard is it to transfer a Perch enabled website from MAMP PRO to a liver server? Do you have any advice for setting up a MAMP PRO server with Perch?
So, do you think the best solution to setup a subdomain to point to my MAMP PRO server? If not, what setup would you recommend?
If you're using MAMP PRO locally, you can set up a new virtual host for each site. (That's what I do for developing Perch.)
When you're ready to show the client, you could put it on a subdomain of a hosting account.
Drew, I purchased a copy of Mamp Pro, but I'm not sure exactly how to setup my website production workflow. Do I simply develop on the Mamp Pro server then, when the site is complete, move everything over to the client's home server?