Installation & Updates

SoftwareSilo distributes Magento packages through a private Composer repository. Composer package names retain the mageb2b/* namespace, while SoftwareSilo is the public product and company brand.

The safest source for commands is Account > Licenses. Expand the licensed extension and copy its installation instructions; the page uses the current repository host, your license token, the packages included in that license and any applicable version limit.

Configure Composer manually

If you need to enter the commands yourself, add bearer authentication and the Composer repository:

composer config bearer.repo.softwaresilo.io '<license-token>'

composer config repositories.softwaresilo composer https://repo.softwaresilo.io/

Then require the exact package listed on the license card:

composer require mageb2b/package-name

Do not paste a real token into tickets, screenshots, logs, committed files or shared shell transcripts. Composer commonly stores credentials in auth.json; keep that file outside source control.

Download the generated instructions

Each expanded license card can download the same installation instructions as a Markdown file. Use this when another authorised team member performs the deployment, but transfer it securely because it contains the license token.

Update an extension

Start by checking the package and allowed version range shown in Account > Licenses:

composer show mageb2b/package-name
composer update mageb2b/package-name --with-dependencies
php bin/magento setup:upgrade
php bin/magento cache:clean

Follow your normal Magento production process for maintenance mode, generated code and static content. Read the extension changelog before updating and take a recoverable database and code backup.

Update access after support expires

An expired support/update period does not make the installed extension stop working. Repository access is limited to versions covered by the licensed subscription window. Renew support and updates from the license card to regain access to newer releases.

Troubleshoot Composer access

Check these in order:

1. The repository host in Composer matches the host shown in your account.
2. The bearer token is the current token for that license.
3. The requested package belongs to the license, including any required add-on.
4. The version is within the update period shown on the license card.
5. Composer is not reading an older global auth.json or repository entry.

Inspect the active configuration without sharing the token:

composer config --list --auth
composer show mageb2b/package-name --all

If the token was rotated, the old value stops working immediately. Update Composer authentication everywhere that license is used.