Download from Git/ko


 * Since MediaWiki 1.19beta2, 1.18.2, 1.17.3, MediaWiki core and extensions use Git for version control. For older versions, see Subversion

Git는 이용자들에게 가장 나중의 버전을 다운로드할 수 있게 해주는 소프트웨어입니다. 이것을 사용하면 미디어위키가 더 빠르게 업데이트되며 업그레이드를 되돌릴 수도 있습니다.

더 자세한 정보를 위해서는 Git를 참조하세요.

전제조건
이것을 사용하기 전에 Git가 필수적으로 설치되어 있어야 합니다. Git 설치 방법은 사용하는 운영체제에 따라 모두 다릅니다. 소스와 공식 바이너리는 이곳 git-scm.com 에서 받으실 수 있습니다. 아니면, 검색 엔진을 이용해 운영 체제의 맞는 설치 지침을 찾아보십시오.

It is recommended that you have composer installed to download and install third party libraries, but not required.

다운로드
You can download MediaWiki core using Git, as well as all extensions currently installed on the Wikimedia Foundation server cluster and many other extensions hosted on.

첫번째 단계는 MediaWiki 레파토리를 복제하는 것입니다. 시간이 소요될 수 있습니다.

In a terminal window, enter the following command:

This clones the entire MediaWiki core repository into a subdirectory named core. To install into a specific directory, add that to the command line (for more info refer to these docs). The default "branch" will be, the cutting-edge, developer version of MediaWiki. Once the repository is cloned, you can easily switch to different branches or tags (see below), including those tracking stable versions of MediaWiki.

Download for development
If you have Developer access (which is easy to request), then instead of cloning anonymously with https you should clone with your ssh  so that you can submit changes for review:



Fetch external libraries
Starting with MediaWiki 1.25, some external libraries that MediaWiki requires are no longer in this "core" git repository. We use composer to manage them. To install these needed libraries, you have a choice:


 * Download and install composer, switch to your core directory and then run composer install --no-dev . Note that if you have an existing composer.lock file you will need to run composer update --no-dev instead.


 * If you don't want to use composer, or if you want to use the same set of vendor libraries as used on the WMF production cluster, you can instead git clone https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git to create a vendor/ directory inside the core folder of your MediaWiki installation. Make sure you use the right branch for your MediaWiki version (e.g. REL1_25 for 1.25).

WMF branches
Remote branches track the MediaWiki versions used on the Wikimedia Foundation server cluster. These may not be entirely stable, but they receive very quick bug fixes and are generally stable enough – after all, these are what major projects such as Wikipedia are using. Once a REL* branch is considered 'stable', we 'tag' it and turn it into a tarball release.

To see what branches are available, switch to your MediaWiki core directory and enter the following command:

Major releases are denoted by "origin/REL ", e.g. "origin/". To switch to a particular release branch:

For example, to switch to the current stable version,, enter:

MediaWiki 태그 (안정화 버전)
Alternatively, specific stable versions of MediaWiki are tracked using 'tags'. These are analogous to the tarball releases. You can see the versions available with:

Using non GNU sort command, such as on Mac OS X, you have to rely on the good old separators:

To use a specific tag:

MediaWiki의 마지막 개발 버전
The latest development version of MediaWiki is tracked in the 'master' branch. This is what is locally checked out by default when you first clone the MediaWiki repository. If you have switched to another branch but would like to switch back to using bleeding-edge MediaWiki, do:

Keeping up to date
If you're using a particular branch or the development version ("master" branch) of MediaWiki, picking up the latest changes is relatively easy. Change into your MediaWiki clone directory and issue the git pull command:

All of the latest changes for the branch you are using will be applied.

The new version of core may require newer versions of extensions and skins, so you must go into each extension and skin directory and update it with a command like git pull --recurse-submodules.

After updating/upgrading you should run the MediaWiki  command-line script to update database tables as needed:

You also need to update mediawiki/vendor to any newer versions of required libraries, see.

If you use MediaWiki-Vagrant, it offers a single command, vagrant git-update, that performs all these steps.

Switching to a different version
Switching to a different version of MediaWiki is far simpler with Git than with SVN. Each of our versions are tracked as branches or tags. In order to switch to one of these, all you have to do is checkout the particular branch or tag you want from within your MediaWiki clone directory:

or

The changes will be applied automatically and you will be all set to go.

Git를 이용한 MediaWiki 확장기능 다운로드

 * List of extensions in git

다운로드

 *  should be replaced with the name of the extension you want to download, without spaces. For Extension:TitleKey, it would be TitleKey. (case sensitive!)

Git에서 확장기능을 내려받고 복제:

Developers clone with:

You can view extension source code in Phabricator's diffusion application, and at the URL:

 https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/.git;a=tree;h=refs/heads/master;hb=master

모든 확장 기능을 다운로드
If you prefer to have all MediaWiki extensions that are at gerrit.wikimedia.org checked out to your machine, enter the following:

Thereafter, to update all extensions to their latest versions, just enter:

To track a specific branch:

If you only need a read-only checkout (for instance to grep or analyse all MediaWiki code), you can use the shared MediaWiki checkout on Labs, without downloading anything on your machines.

Remove an extension
Just remove the extension folder and remove the " " from.

Using Git to download MediaWiki skins

 * List of skins in git

MediaWiki 1.24 and later don't include skins in the Git download.

Follow the exact same procedure as for extensions (described in the previous section), but using  rather than   in all URLs and paths.

Detailed installation instructions are available on each skin's page here on MediaWiki.org, for example see Skin:Vector#Installation. Instructions for all other skins are analogous.

같이 보기

 * Migrating from SVN to Git
 * Nightlies, an alternate to downloading from Git