Commit 9ddbc395 authored by Helmut Hummel's avatar Helmut Hummel
Browse files

[TASK] Change links to use https

Change-Id: I97c63a93d457c12bc182376be798399ce9338fad
parent d9367eb0
<ul class="breadcrumbs">
<li>
<a href="http://typo3.org/" target="_top" title="TYPO3 - The Enterprise Open Source CMS">typo3.org</a>
<a href="https://typo3.org/" target="_top" title="TYPO3 - The Enterprise Open Source CMS">typo3.org</a>
</li>
<li>
<a href="http://typo3.org/download/" target="_top" title="Download">Download</a>
<a href="https://typo3.org/download/" target="_top" title="Download">Download</a>
</li>
<li>TYPO3 CMS Composer Repository</li>
</ul>
......@@ -19,14 +19,14 @@ What Is It?
This is a [composer][1] repository, enabling you to install TYPO3 CMS core and extensions including dependencies via Composer.
This repository includes TYPO3 CMS extensions:
* All TYPO3 Extensions that are uploaded to [TER](http://typo3.org/extensions/repository/) including insecure versions.
* All TYPO3 Extensions that are uploaded to [TER](https://typo3.org/extensions/repository/) including insecure versions.
* Insecure versions are marked in th extra section with "extra""typo3/ter""reviewstate" = "insecure" in the composer extra section
* These extensions are all in the `typo3-ter/` composer namespace
* Extension versions from repositories that are provided on typo3.org [extension setup](http://typo3.org/extensions/extension-keys/)
* Extension versions from repositories that are provided on typo3.org [extension setup](https://typo3.org/extensions/extension-keys/)
* These must be repositories that include a composer.json in each release tag
* The composer name of these releases is determined from the composer.json in these repositories
You can [list and search for](http://composer.typo3.org/satis.html) available extension packages.
You can [list and search for](https://composer.typo3.org/satis.html) available extension packages.
How to use it?
--------------
......@@ -70,7 +70,7 @@ In the example below, this will always get you the most current 6.2.x core of TY
"repositories": [
{
"type": "composer",
"url": "http://composer.typo3.org/"
"url": "https://composer.typo3.org/"
}
],
"require": {
......@@ -91,7 +91,7 @@ dependencies. The file must be placed at the root of your extension and must loo
"name": "vendor-name/my-ext",
"type": "typo3-cms-extension",
"description": "My description comes here",
"homepage": "http://example.com",
"homepage": "https://example.com",
"license": ["GPL-2.0+"],
"keywords": ["TYPO3 CMS", "foo bar"],
"support": {
......@@ -102,7 +102,7 @@ dependencies. The file must be placed at the root of your extension and must loo
The ``vendor-name`` must be one of yours. It must not be "typo3" which is reserved for Core extensions.
There are some [conventions notes](http://wiki.typo3.org/Namespaces#Does_and_don.27ts_for_developers) available in the TYPO3 Wiki related to namespaces.
There are some [conventions notes](https://wiki.typo3.org/Namespaces#Does_and_don.27ts_for_developers) available in the TYPO3 Wiki related to namespaces.
How it works?
-------------
......@@ -112,7 +112,7 @@ We process all ext_emconf.php's (of every non un-secure version) to calculate th
We generate the metadata (packages.json), needed by composer to find the right downloads which will be downloaded from the TER eventually.
[1]: http://getcomposer.org/
[1]: https://getcomposer.org/
[2]: https://getcomposer.org/download/
[3]: http://getcomposer.org/doc/04-schema.md#version
[3]: https://getcomposer.org/doc/04-schema.md#version
[4]: https://git.typo3.org/Sites/ComposerTypo3Org.git
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment