Skip to content

Latest commit

 

History

History
115 lines (89 loc) · 2.73 KB

UPGRADE.md

File metadata and controls

115 lines (89 loc) · 2.73 KB
Raw

UPGRADE

UPGRADE FROM 1.4 to 2.0

  • Require PHP 8.1+
  • Symfony LTS has been changed from 3.4 to 5.4
  • Application composer HOME was changed to %kernel.project_dir%/var/.composer

Run migrations

There are no major BC breaks in the database structure.

Run the command to show SQL changes:

bin/console doctrine:schema:update --dump-sql

Run the command to execute migrations:

bin/console doctrine:schema:update --force

Note Now composer v2 metadata is supported. The app also supports composer v1 too. No additional action required.

Docker UPGRADE

  • Image has been renamed from okvpn/packeton to packeton/packeton
  • Volume directory structure was changed:
    • /data/composer - composer home
    • /data/redis - redis data
    • /data/zipball - dist path
    • /data/ssh - ssh for www-data path

Before:

    - .docker/redis:/var/lib/redis
    - .docker/zipball:/var/www/packagist/app/zipball
    - .docker/composer:/var/www/.composer
    - .docker/ssh:/var/www/.ssh

After:

    - .docker:/data

Env variables update

Before docker-compose.yml

    environment:
        DATABASE_HOST: postgres
        DATABASE_PORT: 5432
        DATABASE_DRIVER: pdo_pgsql
        DATABASE_USER: postgres
        DATABASE_NAME: packagist
        DATABASE_PASSWORD: 123456

After:

    environment:
        DATABASE_URL: mysql://app:!ChangeMe!@127.0.0.1:3306/app?serverVersion=8&charset=utf8mb4

UPGRADE FROM 2.0 to 2.1

The metadata root format /packages.json has been changed. Now it is configurable. By default, for performance it depends on Composer User-Agent If you use /packages.json API directly (without composer) please add query parameter ua=1 for 1 format. See metadata configuration

Before:

{
    "packages": [],
    "notify": "/downloads/%package%",
    "notify-batch": "/downloads/",
    "metadata-changes-url": "/metadata/changes.json",
    "providers-url": "/p/%package%$%hash%.json",
    "metadata-url": "/p2/%package%.json",
    "provider-includes": {
        "p/providers$%hash%.json": {
            "sha256": "af2f8f8f8b403ef309e0aca59b080b65fd7465ede21c12a157a1422af8001f42"
        }
    },
    "available-packages": ["okvpn/cron-bundle"]
}

After:

{
    "packages": [],
    "notify": "/downloads/%package%",
    "notify-batch": "/downloads/",
    "metadata-changes-url": "/metadata/changes.json",
    "providers-url": "/p/%package%$%hash%.json",
    "metadata-url": "/p2/%package%.json",
    "available-packages": ["okvpn/cron-bundle"]
}

The lazy route /p/%package%.json now return Сomposer compatible data:

{"packages": {"name": {versions}}