무들 업그레이드

번역 원본 : https://docs.moodle.org/20/en/Upgrading_Moodle

무들을 한번 설치하면, 다음 버전으로 업그레이드할 수 있도록 설계되어있습니다. 업그레이드 절차는

업그레이드 전에 먼저, 모두 백업합니다. Back up everything.
이전 코드에 새로운 코드를 덮어쓰기 합니다.
관리자 설치 안내 링크 administrator notifications 를 누르면, 셀프업데이트가 시작됩니다.

이상의 과정은 아래에 좀더 자세하게 설명되어있습니다.

때때로, 어떤 버전으로 업그레이드할 때 살펴보아야할 특별한 사항이 있습니다. 따라서, 가능하다면 Upgrading to Moodle 1.6, Upgrading to Moodle 1.8, Upgrading to Moodle 1.9, Upgrading to Moodle 2.0를 살펴보세요. 특히, 추가적인 플러그인이나 커스터마이징된 코드가 있다면 특별히 주의깊게 살펴보아야 합니다.

cpanel을 사용해 무들 업그레이드하기 예시를 살펴보세요. 최신의 자료는 아니지만, 대략적인 과정을 살펴보실 수 있습니다.

[[Ubuntu_Debian_Upgrades|Ubuntu/Kubuntu/Debian 패키지매니져]에 대해서는 별도의 안내 페이지가 있습니다.

무들사이트를 업그레이드하기 위해서는 아래의 절차들을 따라서 진행해야합니다. :

운영하는 무들사이트를 실제로 업그레이드하기 전에 반드시

운영하는 무들사이트 전체를 다른 컴퓨터에 복사해 두시기를 강력히 권장합니다.(Moodle migration를 참고하세요.) 그 후에 업그레이드를 진행하여 제대로 동작하는지 살펴보시기 바랍니다.

요구 사항 확인

새로운 버전을 설치하기 위해서는 다시 한 번 installation documentation를 꼼꼼히 살펴보시기 바랍니다. Administration > Server > Environment 를 눌러 새로운 버전으로 업그레이드하기 위한 요구 사항을 확인하세요.

무들사이트를 관리 모드로 전환하세요

운영중인 무들사이트를 업그레이드하기 전에, 로그인 된 사용자들 중에서 관리자가 아닌 사람들의 서비스를 중지하기 위해 Maintenance Mode를 먼저 눌러 관리 모드로 전환하세요.

중요 데이터 백업

좀더 자세한 사항을 확인하시려면 Site backup를 참고하세요.

업그레이드 전에 백업해야할 3개의 영역이 있습니다.

무들 소프트웨어(예를 들어, server/htdocs/moodle 디렉토리에 들어있는 모든 것)
무들 사이트에 업로드된 파일들(예를 들어, server/moodledata 디렉토리에 들어있는 모든 것)
무들 데이터베이스(예를 들어, SQL 이나 Postgres 데이터베이스)

무들사이트 관리 경험이 있는 관리자들은 큰 변화가 있는 메이져 업그레이드 전에 모든 시스템을 백업해두는 것이 좋다는 것을 알고 있습니다.(실제로 가장 훌륭한 방법입니다.) 실제로, 매일 매일 무들사이트를 백업하도록 백업을 자동화해두는 것이 좋습니다. 대부분의 무들사이트 업그레이드는 표준 무들 패키지를 기준으로 진행되며(사용자가 수정한 코드나 기본 설정 이외의 php 파일들은 업그레이드되지 않습니다.), 업그레이드 도중에 어떤 경고나 메시지도 출력하지 않습니다!!

팁: 다시 한 번 말씀드리지만, "데이터 손실이나 영향에 대해 확실하게 알지 못한다면, 위험하게 시도하지 마십시오" : 정기적으로 백업하고, 실제로 어떻게 백업되고 있는지 확인하세요!

Install the new Moodle software

Upgrading can be a simple process or a more complicated process. Sites that have not used contributed code and are migrating from say Moodle 1.x.1 to 1.x.3 should not have a problem. However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.

Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.

Standard install package

Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.

It is probably a good idea to use the Site administration block>Server>Maintenance mode to prevent user activity as the site upgrades.
Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
Copy your old config.php file back to the new Moodle directory.
If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet).
Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.
After a successful upgrade, turn off the maintenance mode, so your users can get into the site.

Using a downloaded archive

In some installs, the site administrator may overwrite the Moodle code with a backup copy. Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders).

Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or "cleaned" installations. The best way is to rename the current Moodle code directory (for example rename "moodle" to "moodleold"), then unpack the new Moodle archive into the old location (for example, a new directory called "moodle").

Linux

mv moodle moodle.backup
tar xvzf moodle-1.1.tgz

Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one (check that optional/custom plugins are the correct version for your new Moodle first):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to

sudo chown www-data moodle/config.php

if necessary.

where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'. You can find out by doing 'ls -l' in your /var/www/moodle folder (or wherever your moodle site is) and then looking at the owner and group.

so you may see something like

ls -l
...lots of lines...
-rw-r--r--   1 apache system     784 Jun 28  2007 config.php 
...lots more lines...

so the owner is apache and the group is system.

To replicate this on your new system you can do 'chown apache:system config.php'

or to do a whole group do

chown apache:system ./*

and recursively

chown -R apache:system ./*

Using CVS

You can use CVS for updating or upgrading your Moodle. First you need to do a CVS checkout in your (empty) Moodle root directory.

You can use any of our CVS Mirror servers. Just replace SERVER.cvs.moodle.org in the instructions below with the name of the mirror server you chose!.

For Linux servers

To do a CVS checkout of Moodle, you first have to logon to the Moodle CVS server.

 cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login
 No password for anonymous, so just hit the Enter button.

Go to the directory where you want the Moodle root to come and type

 cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle 
 (where MOODLE_18_STABLE is the desired version)

To update, just go into the Moodle root directory and update to the new files:

 cvs update -dP

To update to a new version type in the following and change 18 to whatever newest version upgrade number is

 cvs -Q update -dP -r MOODLE_18_STABLE

Make sure you use the "d" parameter to create new directories if necessary, and the "P" parameter to prune empty directories.

For Windows servers

You can use Tortoise CVS to do the initial checkout and the updates.

If you have been editing Moodle files, watch the messages very closely for possible conflicts. All your customised themes and non-standard plugins will be untouched.

Do not forget to trigger the install process in the site administration block (see below).

Using Git

You can use Git for updating or upgrading your Moodle. First you need to do a Git checkout in your (empty) Moodle root directory.

See Git for Administrators for further details.

Finishing the upgrade

The last step is to trigger the upgrade processes within Moodle.

To do this just visit the Site administration block admin page (or http://example.com/moodle/admin) and the "Notifications" link.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

TIP: Use the site administration block>Server>Maintenance mode to prevent users from changing data during the upgrade.

TIP: If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing. Post a thread or check the Installation problems forum and check Tracker for potential issues.

Verify the upgrade (optional)

If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at Verify Database Schema.

Upgrading more than one version

In general, it is recommended to upgrade via the newest of each major version of Moodle, for example 1.7 -> 1.9. An exception to this is when upgrading from 1.5 or 1.6, when it is recommended that 1.7 and 1.8 are skipped, in other words upgrade 1.5 -> 1.6 -> 1.9. (The main reason for this recommendation is that the default roles settings obtained when upgrading to 1.7 are not ideal for 1.8 onwards, 1.8 has problems with groups, etc.)

Documentation