Moodle 2.6+
I currently have a moodle site domain1.com that points to /var/www/moodle, I just purchased domain2.com and would like it to point to a completely new moodle instance.
Before I proceed to copy my code base, create a new mySQL database and mess with apache's virtual server settings per this thread, I wanted to make sure that I shouldn't be using Moodle Instance Management instead. MIM seems like it is for use under a subdomain, not a completely new domain.
Correct? Any tips?
Ben
Yes,
You are right. As you already created a new database, You just have to give a new folder location for moodledata directory. And yes these two moodle instance will be separate one.
And yes Moodle Instance Management will not be there.
Best regards,
PD
I think Moodle Instance Management is probably for if you are crazy
Yes - just create a separate installation and get bust with virtual hosts.
I have a setup like this...
/var/www/www.domain1.com/...
/var/www/www.domain2.com/...
/var/moodledata/www.domain1.com/...
/var/moodledata/www.domain2.com/..
Then two databases and appropriate vhosts defined in Apache. As long as you can work Apache, it's simple.
What are the implications of renaming my original moodle folder to /var/www/www.domain1.com/
Off the top of my head, I'll have to change my apache DocumentRoot for that virtualhost - but is that all?
I wouldn't recommend it though. Then again it depends on if both sites are public. if he has one website that's public and one that's closed. Wouldn't it be advisable that both sites be housed on two separate servers.
Why?
It depends how you define public and (in particular) closed. What 's closed about it? You can do a lot with Apache.
Examples
I have one moodle instance where anyone looking for a job goes on applies and take the testing required. They learn about the job and the company etc. So that is open to the public as thousands of people nail this one. Nothing specific is saved here. This instance anyone can register.
The second instance is where employees register, this is linked to there active directory. This instance is loaded up with even more security. Employees go on and take mandatory exams that are job specific. They can learn about there job roles etc. This one is IP address specific.
Many of books and comments I've read all suggest its not a good idea to house both of these in the same place. Especially since they are drastically different from the other. They are day and night so to speak.
You can restrict in Apache through IP address. You have to ask if you need so much security that you need the trouble of two servers (presumably one on your intranet and one on your DMZ or whatever...)
Yes it is restricted to block external IPs on one site via apache. Also, on the other one It needs to be open. Since people can stop by register with their own email accounts. Yes that level of security is needed for the one site as serious information is located on there. It is extremely locked down.
