Okay, so I’ve successfully transitioned my Freeway Pro/Perch website from a folder buried two levels beneath the main directory of my website to a subdomain.
When I setup the subdomain I created a Client1 folder below my my main domain. In hindsight it would have been better to have a main subdirectory with all of my client files, so in this case I should have set it up as Clients/Client1.
My question is after I create the corrected subdomain, can I simply pickup the entire contents of Client1 and move them to Clients/Client1 without anything going haywire (i.e. Perch database links)?
My question is after I create the corrected subdomain, can I simply pickup the entire contents of Client1 and move them to Clients/Client1 without anything going haywire (i.e. Perch database links)?
If I understand you correctly (and I might not), by placing the site in a sub-directory (Client1) of the sub-domain (Clients) you will have the same problem as if you had bypassed the sub-domain process and simply created a regular “Client1” sub-directory in the site root; you’re still one level below where you want to be. The intent is to stop creating sub-directories because it screws around with your paths but that’s exactly what you’re doing with /Clients/Client1/. Stick with “Clients” and you should be ok.
Since you probably get unlimited sub-domains I would create a new sub-domain for each client and stop creating sub-directories within those sub-domains.
No, actually the way subdomains work with godaddy is you create whatever subdomain you want, but then the actual files exists in a subdirectory within your main site.
For example when I setup the subdomain client1.idealynx.com I have to tell godaddy where I want to store the files. In this case, I have them in idealynx.com/client1. The files still think they’re at the top-level of client1.idealynx.com, which means all of the links stay intact, especially when I move the site off of my development server to its own domain.
However, to keep everything nice and neat, I think I’d prefer to have all of my client files stored the way I’m accustomed, which is clients/client1, clients/client2, etc.
By the way, when I upload files to the server I have to put them in whatever subdirectory I create. Are you confused yet? I am.
Now, how do I move the SQL database when I move the website to its new, permanent domain? Can I simply drag and drop it to the new server then update my Perch config.php file?
Can I simply drag and drop it to the new server then update my Perch config.php file?
No with regard to drag-n-drop. Remember, I told you the other day that you need to export the contents of the local db using Sequel Pro or phpMyAdmin or some other db admin tool. You’ll then have a single .sql file which you can then import the remote db.
Lot of stuff here, but what I really like is I can see the field names for all of the Perch served data. This is all starting to make a whole lot more sense to me. It’s kinda like I pulled the curtain back on the Wizard of Oz.
Very cool stuff, although admittedly way over my head.
Lot of stuff here, but what I really like is I can see the field names for all of the Perch served data. This is all starting to make a whole lot more sense to me. It’s kinda like I pulled the curtain back on the Wizard of Oz.
Very cool stuff, although admittedly way over my head.
Don’t forget that you can also use Coda’s built-in MySQL tool.
You’ll find that Sequel Pro (or whatever tool you use) is invaluable when doing any sort of db work. Gotta have it.
See, looking behind the curtain isn’t nearly as scary you thought. Right? Just be careful when manually editing anything in a db, it’s a one-way trip. Backup, backup, backup first.
I thought you might be interested to know that I renamed one of the folders that contained Perch served content from “resources” to “extras”. I did this to avoid any possible conflicts with Freeway pro’s “Resources” folders.
Anyway, as you may have guessed already, when I did that I lost all of my Perch data. Well, actually I didn’t lose it, Perch didn’t recognize it because I renamed the folder. Anyway, I used Sequel Pro to copy the data from the old Perch file to the new one. Worked like a charm, and I would have never had they capability had you not recommended Sequel Pro.
Thanks Dude. That’s twice you’ve saved my butt today.
On 5 Jul 2012, 5:09 am, Todd wrote:
Remember, I told you the other day that you need to export the contents of the local db using Sequel Pro or phpMyAdmin or some other db admin tool. You’ll then have a single .sql file which you can then import the remote db.
You’re welcome. Glad to hear you got it sorted out.
Two things to know:
The Perch resources folder resides in the “perch” folder, below where FW puts its Resources folder.
Freeway uses "R"esources and Perch uses "r"esources. My guess is that even if both folders existed at the same level they wouldn’t conflict with one another because the directory naming convention for servers is (I believe) usually case-sensitive.
Todd
On Jul 5, 2012, at 1:44 PM, RavenManiac wrote:
Hey Todd,
I thought you might be interested to know that I renamed one of the folders that contained Perch served content from “resources” to “extras”. I did this to avoid any possible conflicts with Freeway pro’s “Resources” folders.
Anyway, as you may have guessed already, when I did that I lost all of my Perch data. Well, actually I didn’t lose it, Perch didn’t recognize it because I renamed the folder. Anyway, I used Sequel Pro to copy the data from the old Perch file to the new one. Worked like a charm, and I would have never had they capability had you not recommended Sequel Pro.
Thanks Dude. That’s twice you’ve saved my butt today.
On 5 Jul 2012, 5:09 am, Todd wrote:
Remember, I told you the other day that you need to export the contents of the local db using Sequel Pro or phpMyAdmin or some other db admin tool. You’ll then have a single .sql file which you can then import the remote db.
Yeah, I knew that, but there is a FWP option to switch all of the folders to lowercase, which I use from time to time, so I just wanted to avoid that possibility.
On 5 Jul 2012, 7:48 pm, Todd wrote:
You’re welcome. Glad to hear you got it sorted out.
Two things to know:
The Perch resources folder resides in the “perch” folder, below where FW puts its Resources folder.
Freeway uses "R"esources and Perch uses "r"esources. My guess is that even if both folders existed at the same level they wouldn’t conflict with one another because the directory naming convention for servers is (I believe) usually case-sensitive.
