Difference between revisions of "Administrator do's and don'ts"

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 3.1. Up-to-date documentation for the latest stable version of Moodle is probably available here: Administrator do's and don'ts.

m (link to Japanese)
(reformat, add links, remove stub)
 
Line 1: Line 1:
 +
==Use a special course for imported backup files for new courses==
 
Don't use the files area in the main Moodle site course to restore course archives.  You can destroy the front page very easily.  You will be much better off to set up a special course just for that purpose!
 
Don't use the files area in the main Moodle site course to restore course archives.  You can destroy the front page very easily.  You will be much better off to set up a special course just for that purpose!
  
: Why? How? --[[User:David Mudrak|David Mudrak]] 09:43, 10 September 2008 (CDT)
+
:: Accidentally restoring a faulty course archive to your main site course will break the whole site for everyone. Also -- by default, all users have access to the files in the main site course. If your course archive contains any confidential information, you're potentially exposing it to all site users.  
:: Accidentally restoring a faulty course archive to your main site course will break the whole site for everyone. Also -- by default, all users have access to the files in the main site course. If your course archive contains any confidential information, you're potentially exposing it to all site users. We have hidden test courses that we use to host the course archives we're going to restore. --[[User:Donna Hrynkiw|Donna Hrynkiw]] 13:11, 17 November 2008 (CST)
 
  
 +
::Do create a hidden course to host the course archives your going to restore. Put your backups from other sites in that hidden courses files.  Then restore the course from that backup.
  
 +
==Do use a non production site for testing==
 +
Many consider a localhost to be a beautiful thing.  You can break it and not worry about impacting your production site. For example, not sure about how a plugin is going to work? Download your production code files into a localhost, change the moodle config.php file and find out.
  
'''For a much more complete set of Administrator's do's and don'ts, you may want to consider [[Beginning Administration FAQ]].'''
+
 
 +
==See also==
 +
*[[Administration FAQ]]
 +
*'''For a much more complete set of Administrator's do's and don'ts, you may want to consider [[Beginning Administration FAQ]].'''
  
  
Line 12: Line 18:
  
 
[[Category:Administrator]]
 
[[Category:Administrator]]
 
{{stub}}
 

Latest revision as of 17:57, 18 December 2010

Use a special course for imported backup files for new courses

Don't use the files area in the main Moodle site course to restore course archives. You can destroy the front page very easily. You will be much better off to set up a special course just for that purpose!

Accidentally restoring a faulty course archive to your main site course will break the whole site for everyone. Also -- by default, all users have access to the files in the main site course. If your course archive contains any confidential information, you're potentially exposing it to all site users.
Do create a hidden course to host the course archives your going to restore. Put your backups from other sites in that hidden courses files. Then restore the course from that backup.

Do use a non production site for testing

Many consider a localhost to be a beautiful thing. You can break it and not worry about impacting your production site. For example, not sure about how a plugin is going to work? Download your production code files into a localhost, change the moodle config.php file and find out.


See also