Introducing a faster, Composer 2.0 ready Enterprise package repository

12/01/2021, 08:37
| 3 Min read
André Rømcke & Mateusz Bieniek (Sr. Support Engineer)
Introducing a faster, Composer 2.0 ready Enterprise package repository

Together with the Ibexa DXP 3.3LTS release, we are launching updates.ibexa.co. It’s a new Composer v2 ready packages repository for our Enterprise packages, available for all supported versions of our software still within service life. With this post we’ll define when our previous package repository, updates.ez.no, will be phased out.

2021 is here and 3.3LTS is our latest and greatest, at time of writing in RC2. And as part of it we’ve worked on our infrastructure for Composer and Flex in order to facilitate the new Symfony Flex based release.

Last fall Composer v2 came out, and with-it massive performance and memory usage improvements.

With 3.3LTS, Composer v2 is not only supported, but required. And for older releases it is hereby not only supported, but also optimized for.

The new updates.ibexa.co composer repository

updates.ibexa.co is a new drop-in replacement for excising updates.ez.no composer repository, for Ibexa DXP/Enterprise packages (and older releases within service life).

It comes with the following benefits:

  • Even faster when running composer update
  • Dual license packages
    • No more need to use separate “/ttl” and “/bul” composer repositories
    • Seamless upgrade from Trial
  • Per package permissions
    • No need for several composer repositories per product level
      • Faster when on Ibexa Experience & Commerce
    • Seamless upgrade/downgrade between Ibexa DXP flavors.

How to start using it today

Moving over to updates.ibexa.co is easy, if you are on a maintained software release from Ibexa you can mover over today in the following two ways:
A.    During Composer update
    i.    Change composer.json to point to https://updates.ibexa.co
        i.    NOTE: No additional path in URI
    ii.    Run composer update
        i.    The first time you’ll be asked to enter credentials for updates.ibexa.co, you can use the same credentials you used for updates.ez.no in the past

    If you’d like you can do this using the following command line commands:

$ perl -i -p -e 's@"https://updates.ez.no/[^/]+/?"@"https://updates.ibexa.co"@' composer.json
$ composer update

B.    Swap without performing updates to packages
    i.    Change composer.json and composer.lock to point to https://updates.ibexa.co
        i.    NOTE: No additional path in URI
    ii.    Run composer install
        i.    On existing install, rename “vendor” folder to verify download succeeds
        ii.    The first time you’ll be asked to enter credentials for updates.ibexa.co, you can use the same credentials you used for updates.ez.no in the past

    You may accomplish this using the following command line commands:

$ perl -i -p -e 's@"https://updates.ez.no/[^/]+/?"@"https://updates.ibexa.co"@' composer.json
$ perl -i -p -e 's@"https://updates.ez.no/[A-Za-z0-9_]+/([^"]+)"@"https://updates.ibexa.co/$1"@' \
composer.lock
$ composer install

What will happen to Updates.ez.no?

    •    Build of new packages is as of now only done nightly
    •    Becomes an archive on July 31, 2021
        o    The service will be renamed to archive-updates.ez.no
        o    No new packages will be built
        o    Traffic coming to updates.ez.no will be redirected to the new updates.ibexa.co.
As shown in section above about how you can move over, updates.ibexa.co is a drop-in replacement for any package versions on releases still within service life. So, this change should not in any way affect you negatively.

Moving to archive-updates.ez.no for releases outside of service life

Only situations where you’ll need to adapt your setup and use archive-updates.ez.no is if you are running eZ software which is no longer within service life.
archive-updates.ez.no has not been setup yet, however once it is, the procedure is similar to instructions above. URL in composer.json and composer.lock will need to be updates, example:
    -    https://updates.ez.no/bul becomes https://archive-updates.ez.no/bul

What’s next?

You’ll already be able to use this today, as it will provide several benefits to developers involved in your Ibexa DXP or older eZ Platform Enterprise project. In the future look out for blog posts about what technologies are in use in the new updates.ibexa.co, support.ibexa.,co and flex.ibexa.co architecture, until then, all good wishes for a Happy New Year!

 

Insights and News