All Collections
FAQ
Migrate from gitlab.com to blackswift.cloud
Migrate from gitlab.com to blackswift.cloud

Front-Commerce is relocating its codebase to blackswift.cloud due to Gitlab pricing changes. Here are the impacts for you.

Pierre avatar
Written by Pierre
Updated over a week ago

Earlier this year, Gitlab announced a new pricing that will take place on the 19th of october 2022. As for many other users, this new pricing is not adapted to our context.

We discovered this information in september and have been trying to find the best solution since then.

We've decided to migrate our repositories and users from Gitlab.com to another Gitlab SaaS provider: Blackswift 🇫🇷. We'll keep providing you the code and everything you already know… the only difference is the domain name!

Instead of accessing Front-Commerce projects at https://gitlab.com/front-commerce, you must now use https://gitlab.blackswift.cloud/front-commerce.

This page contains all the information you'll need to update your project's dependencies (npm / composer) and deployment/CI pipelines.

User accounts

You will receive invitations to Blackswift.cloud from us. We will invite you to your same current user group(s), using your work email address.

After accepting the invite, you should be able to view all Front-Commerce projects.

⚠️ Don't forget to create your SSH keys in your Blackswift Gitlab account:

Every team has one or more Owner. These people can invite new teammates if needed.

We will contact you when the migration has been completed on our side so you can start the migration process.

In case of problems or questions, don't hesitate to contact us!

Update project dependencies

We know that modifying a codebase could be tedious for a project. We're sorry that we had to require this from you and hope it won't be needed anytime soon!

In your Front-Commerce project (Javascript)

To update your Front-Commerce dependencie(s) you must run npm install module/url#version with the same version than the one you're currently depending on in your project.

See the list of modules / URLs below to help you in this process.

Front-Commerce core:

npm install git@gitlab.blackswift.cloud:front-commerce/front-commerce.git#X.Y.Z

Wordpress module:

npm install git@gitlab.blackswift.cloud:front-commerce/front-commerce-wordpress.git#2.17.1

Prismic module: ⚠️ This module shouldn't be used anymore if you're using Front-Commerce 2.18+. Please follow our migration guide instead.

npm install git@gitlab.blackswift.cloud:front-commerce/front-commerce-prismic.git#1.0.0-beta.12

💡 Some users reported that they add to use gitlab.blackswift.cloud/front-commerce/front-commerce instead of gitlab.blackswift.cloud:front-commerce/front-commerce (replacing : with /) in some contexts. It could be related to the npm version. Let us know if you get this issue.

In your Magento project (PHP)

To update your Front-Commerce dependencie(s) you must:

  • update the composer repositories URLs (composer config repositories.xxx git git@gitlab.blackswift.cloud:front-commerce/yyy)

  • update your lockfile by running composer update front-commerce/*

See the list of modules / URLs below to help you in this process.

Magento2 OpenSource module:

composer config repositories.front-commerce git \
git@gitlab.blackswift.cloud:front-commerce/magento2-module-front-commerce.git

Magento2 Commerce module:

composer config repositories.front-commerce-magento2-commerce git \
git@gitlab.blackswift.cloud:front-commerce/magento2-commerce-module-front-commerce.git

Magento2 B2B module:

composer config repositories.front-commerce-magento2-b2b git \
git@gitlab.blackswift.cloud:front-commerce/magento2-b2b-module-front-commerce.git

Magento1 CE / OpenMage module:

composer config repositories.front-commerce git \
git@gitlab.blackswift.cloud:front-commerce/magento1-module-front-commerce.git

Magento1 EE module:

composer config repositories.front-commerce-ee git \
git@gitlab.blackswift.cloud:front-commerce/magento1-module-enterprise-front-commerce.git

When repositories have been updated in your composer.json (with the above commands), don't forget to update your lockfile:

composer update front-commerce/*

💡 You can use grep "gitlab.com" composer.* to ensure there are no leftovers of Front-Commerce Gitlab.com url in your dependencies.

Update internal documentation (optional)

We've done our best to keep URLs as similar as possible (Cool URIs don't change!). Updating references to our Gitlab.com code should be as simple as replacing gitlab.com/front-commerce with gitlab.blackswift.cloud/front-commerce.

Don't forget to update:

  • your internal documentations (Notion, Confluence…)

  • issue trackers (Jira, Redmine, Linear…)

  • comments in your codebase

Did this answer your question?