iJoomla Forum

iJoomla Magazine => Tips and Tricks => Topic started by: Rob Joyce on November 21, 2007, 09:32:04 PM



Title: Licenses and deploying from dev to production sites
Post by: Rob Joyce on November 21, 2007, 09:32:04 PM
many people have asked me:"how does the licenesing effect my site when I move my site from dev to production"
Well, here's how you do it.

The following example is for development locally, demo to your clients on a dev server, then deployment to the clients production server.
  If you enter livesite.com as your dev domain field, then download the component.
When downloading, enter 'dev' in the subdomains box.
This will allow you to use the component on:
http://127.0.0.1  (local development)
http://localhost  (local development)
http://livesite.com (production OR demo site)
http://www.livesite.com (production OR demo site)
http://dev.livesite.com (dev site)
http://www.dev.livesite.com (dev site)

THEN, when your client is happy, you simply enter the Prod domain name in our system and download the component again.
Extract the downloaded file.
If you have simply MOVED your site to a new domain for your client, you need to extract the license.txt file from the component zip file and replace the license.txt file on the production site.
The license file is located in the /administrator/components/com_magazine directory
(this assumes the component is iJoomla magazine)

Now, you many be asking, "But how do I move my site?"
Here's how.
You can buy a third party component names JoomlaCloner, but I find it to be very buggy and hart to use.
The manual method is...
1) Export your database via phpmyadmin (from your cpanel or plesk)
2) create a new database on the new server.
3) Import this exported dbase on your new server.
4) Zip the entire website into an archive. (use JoomlaXplorer)
5) Upload this file to the new site and unzip it.
(Note, you may have a problem with file ownership and permissions, so you might need tech support to reset them for you)
6) modify the configuration.php file to suit the paths on the new server and the new database parameters.
Your site should now be working.
If I've missed anything, please let me know and I'll update this article.


Title: Re: Licenses and deploying from dev to production sites
Post by: RicardoCorai on November 22, 2007, 01:46:11 PM
Thank you Robbo.
Very useful!


Title: Re: Licenses and deploying from dev to production sites
Post by: Larks on May 03, 2008, 09:46:23 AM
I have an active site with a different CMS system on it.

In theory, couldnt I create a DB on my server, then load and create magazine site on dev.mydomain.com and then only have to move the files and update the license since the DB info wont be changing?


Title: Re: Licenses and deploying from dev to production sites
Post by: RicardoCorai on May 12, 2008, 10:49:46 AM
I have an active site with a different CMS system on it.

In theory, couldnt I create a DB on my server, then load and create magazine site on dev.mydomain.com and then only have to move the files and update the license since the DB info wont be changing?
No, you will need to reinstall the extension.
Best regards,