Download the PHP package akeneo/transporteo without Composer

On this page you can find all versions of the php package akeneo/transporteo. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of akeneo/transporteo

Informations about the package transporteo

Transporteo

Goal

This tool aims at helping you to migrate your PIM 1.7 standard edition (either Community or Enterprise) to the new version 2.0. All your data will be migrated seamlessly. Your source PIM won't be updated nor touched. Instead, we'll perform the migration in a brand new PIM 2.0. Several reasons led us to this choice:

The 1.7 source PIM you will migrate from can be either installed locally or remotely.

The 2.0 destination PIM you will migrate to should be installed locally running on the port 80, you can install it following these instructions. The minimum version of the destination PIM is 2.0.3.

Both PIM should be functionnal and have a functionnal API with admin rights.

Before proceeding, we strongly encourage you to read our documentation and our functional and technical blog posts about the version 2.0:

Scope

This tool has a dedicated release cycle and we're regularly releasing improvements in new versions.

We count on your feedback to continue to improve it in attempt to cover all your migration needs, don't hesitate to open issues describing your cases.

Data Migration

Edition Model Version
Community Association type 1.0.0
Community Attribute 1.0.0
Community Attribute Group 1.0.0
Community Categories 1.0.0
Community Family 1.0.0
Community Group type 1.0.0
Community Group 1.0.0
Community Reference Data 1.0.0
Community Product 1.0.0
Community User 1.0.0
Community User Roles 1.0.0
Community User Groups 1.0.0
Community Access Control List 1.0.0
Community Variant Group 1.0.0
Community Product History Not supported
Community Image files See this section
Enterprise Product Asset 1.0.0
Enterprise Asset files See this section
Enterprise Product Asset Categories 1.0.0
Enterprise Product Rules 1.0.0
Enterprise Product Draft Not supported
Enterprise Published Product Not supported
Enterprise Teamwork Assistant Not supported

Extensions

Extension Version
ElasticSearchBundle Not relevant as ElasticSearch is now part of the native stack
InnerVariationBundle 1.0.0
CustomEntityBundle Not supported

Custom Code

For now, the custom code migration is not automated.

Our plan is to enrich Transporteo with a step by step assistant to help you updating your custom code.

Image and asset files

If your images and assets are configured on a remote file system, you just have to configure you 2.0 PIM to access them. If your images and assets are configured to be stored locally, you have to copy them manually into the 2.0 PIM.

Installation

How to use

To launch the tool, run:

then, let yourself be guided ;)

At the end of the tool's job, you will have your database setup with your data but we do not migrate your custom code. You will have to migrate it following this upgrade file.

We plan to automate this part in future release, stay tuned! :)

Documentation

Support & contribution

Be aware that this tool is only supported in best effort by our team. If you find an issue or want to ask for an improvement, do not hesitate to open a Github issue on this repository.

All contributions are of course very welcomed! So do not hesitate to help us build an even better migration tool. We'd love that. You can have a look to the Contributing page.

All versions of transporteo with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1.0
cypresslab/gitelephant Version ~1.0
monolog/monolog Version ^1.23
php-ds/php-ds Version 1.1.1
symfony/config Version 3.3.4
symfony/console Version 3.3.4
symfony/event-dispatcher Version 3.3.4
symfony/dependency-injection Version 3.3.4
symfony/filesystem Version 3.3.4
symfony/workflow Version 3.3.4
symfony/translation Version 3.3.4
symfony/monolog-bridge Version ~3.4
akeneo/api-php-client Version ~1.0
php-http/guzzle6-adapter Version ~1.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package akeneo/transporteo contains the following files

Loading the files please wait ....