PHPackages kiboko/bisous - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. kiboko/bisous ActiveProject kiboko/bisous ============= v1.0.3(6y ago)52[3 PRs](https://github.com/kiboko-labs/bisous/pulls)PHPPHP ^7.2 Since Oct 21Pushed 4y ago4 watchersCompare [ Source](https://github.com/kiboko-labs/bisous)[ Packagist](https://packagist.org/packages/kiboko/bisous)[ RSS](/packages/kiboko-bisous/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (4)Dependencies (12)Versions (10)Used By (0) Akeneo Fixtures Generation Toolbox ================================== [](#akeneo-fixtures-generation-toolbox) This toolbox helps generating CSV fixtures consumed by Akeneo's InstallerBundle from Magento 1.9CE or 1.14EE catalog data. This package is here to help you import your Magento catalog into a fresh new Akeneo instance. It is not aimed at synchronising on a daily basis Akeneo and Magento together. Be aware that all your existing Akeneo product data will be reset by this tool, and lost. Supported attribute types ------------------------- [](#supported-attribute-types) Magento TypeAkeneo TypeNot Localizable, not ScopableLocalizable, not ScopableNot Localizable, ScopableLocalizable, ScopableGalleryAsset Collection❌❌❌❌Gallery ItemImage✅✅✅✅DatetimeDate✅✅✅✅FileFile❌❌❌❌SKUIdentifier✅❌❌❌ImageImage✅✅✅✅DecimalMetric❌❌❌❌MultiselectMulti select✅❌❌✅SelectSimple select✅❌✅✅NumberNumber❌❌❌❌PricePrice❌❌❌❌StatusSimple select❌❌❌✅-Ref. multi select❌❌❌❌-Ref. simple select❌❌❌❌TextText area✅❌❌✅VarcharText✅❌❌✅VisibilitySimple select❌❌❌✅YesNoYes No❌❌❌❌How to start ------------ [](#how-to-start) ### Install using Composer [](#install-using-composer) You will primarily need to install the tool in your environment: `composer global require kiboko/bisous` Once you are done, open a terminal in your Akeneo environement. You will need to create an `.env` file, with the following environment variables properly set: - `APP_DSN=mysql:host=mysql;dbname=magento`, Magento's database connection DSN, see [PDO MySQL Data Source Name](https://www.php.net/manual/en/ref.pdo-mysql.connection.php) - `APP_USERNAME=root`, Magento's MySQL user name - `APP_PASSWORD=password`, Magento's MySQL password You will then need to create a `catalog.yml` file in this directory, describing your catalog structure. See [The `catalog.yml` file](#the-catalogyml-file) ### Download the phar from github [](#download-the-phar-from-github) Go to [the latest version download page](https://github.com/kiboko-labs/bisous/releases/latest) and download the `bisous.phar` and `bisous.phar.pubkey` files. Alternatively you can install the files this way: ``` curl -L https://github.com/kiboko-labs/bisous/releases/download/v1.0.0/bisous.phar --output /usr/local/bin/bisous curl -L https://github.com/kiboko-labs/bisous/releases/download/v1.0.0/bisous.phar.pubkey --output /usr/local/bin/bisous.pubkey chmod 0755 /usr/local/bin/bisous ``` Run the tool ------------ [](#run-the-tool) Once properly installed, run `bisous magento /src/InstallerBundle/Resources/fixtures/default`. This command will create fixtures file required by Akeneo, with your Magento catalog data and structure. Available commands ------------------ [](#available-commands) ### Configuration commands [](#configuration-commands) - `init` Creates an initial configuration file from Magento configuration. - `test` Tests the syntax of the configuration file. ### Testing commands [](#testing-commands) - `fake-medias` Generate fake or minimal image files from the products.csv and product\_models.csv files. ### Fixtures-generation commands [](#fixtures-generation-commands) - `magento` Generate the fixtures files depending on your catalog.yaml configuration and your Magento data. - `magento:attribute-options` same, but only attribute options - `magento:attribute-groups` same, but only attribute groups - `magento:attributes` same, but only attributes - `magento:channels` same, but only channels - `magento:families` same, but only families - `magento:locales` same, but only locales - `magento:products` same, but only products ### Internal commands [](#internal-commands) - `help` Display command help - `list` Lists all commands available - `self-update` Update the `bisous` command to the latest available The `catalog.yml` file ---------------------- [](#the-catalogyml-file) The `catalog.yml` file has a root node named `catalog:`, and 5 sub-nodes described in the following paragraphs: ### The `attributes:` section [](#the-attributes-section) This section is useful for describing your attribute list. It is an array of configuration fields, with the following fields: - `code` (string): Your attribute code, as seen in Akeneo - `type` (string): The attribute's type (valid values are `identifier`, `text`, `text-area`, `rich-text`, `status`, `visibility`, `simple-select`, `multiple-select`, `datetime`, `metric`, `image`, `image-gallery-item`) - `strategy` (string): The import strategy, following the next possible values: - `ad-hoc`: the attribute will be created in Akeneo in the same way it was created in Magento - `aliased`: the attrib ute will be created in Akeneo with another code than the one existing in Magento - `ex-nihilo`: the attribute will be created in Akeneo without taking into account any attribute present in Magento - `group` (string): the attribute group in which the attribute will be assigned in Akeneo - `source` (string) (for strategy `aliased` only): the attribute code in Magento - `position` (string) (for attribute type `image-gallery-item` only): the image index in the Magento media gallery - `scoped` (bool): to specify it the attribute is scopable (only applies to types `text`, `text-area`, `rich-text`, `status`, `visibility`, `simple-select`, `multiple-select`, `datetime`, `metric`, `image`, will produce an error in Akeneo if used on a variant axis attribute) - `localised` (bool): to specify it the attribute is localizable (only applies to types `text`, `text-area`, `rich-text`, `status`, `visibility`, `simple-select`, `multiple-select`, `datetime`, `metric`, `image`, will produce an error in Akeneo if used on a variant axis attribute) Example: ``` catalog: attributes: - code: sku type: identifier strategy: ad-hoc group: general - code: name type: text strategy: ad-hoc group: marketing scoped: true localised: true - code: variation_name type: text strategy: ex-nihilo group: marketing scoped: true localised: true - code: weight type: metric strategy: ad-hoc group: logistics metric: family: Weight unit: KILOGRAM - code: image type: image strategy: ad-hoc group: marketing - code: alternative_image_1 type: image-gallery-item strategy: aliased group: marketing source: media_gallery position: 1 - code: alternative_image_2 type: image-gallery-item strategy: aliased group: marketing source: media_gallery position: 2 ``` ### The `groups:` section [](#the-groups-section) This section describes the attribute groups that will be created in Akeneo, with the following fields: - `code` (string): it will contain the attribute group code in Akeneo - `label` (array): it contains a map of the labels of this group, having key as locale ISO code and value as actual label. Example: ``` catalog: groups: - code: general label: fr_FR: Général en_GB: General - code: marketing label: fr_FR: Général en_GB: General ``` ### The `families:` section [](#the-families-section) Example: ``` catalog: families: - code: jeans attributes: [ name, description, short_description, meta_title, meta_description, status, visibility, image, variation_name, variation_image, variation_description, news_to_date, news_from_date, length, width, color, size ] label: name image: image requirements: - scope: america attributes: [ name, description, image ] - scope: europe attributes: [ name, description, image ] - scope: france attributes: [ name, description, image ] - scope: japan attributes: [ name, description, image ] - scope: china attributes: [ name, description, image ] - scope: asia attributes: [ name, description, image ] - scope: amazon attributes: [ name, description, image ] - scope: ebay attributes: [ name, description, image ] variations: - code: jeans_by_size_and_color skuPattern: '{{ parent }}:{{ length }}:{{ width }}' level-1: axis: [ length, width ] attributes: [ variation_name, variation_image, variation_description, news_from_date, news_to_date ] level-2: axis: [ color ] attributes: [ sku, status, visibility ] - code: jeans_by_size level-1: axis: [ size ] attributes: [ sku, status, visibility, variation_name, variation_image, variation_description, news_from_date, news_to_date ] ``` ### The `locales:` section [](#the-locales-section) Example: ``` catalog: locales: - code: fr_FR currency: EUR store: 15 - code: en_GB currency: GBP store: 21 ``` ### The `scopes:` section [](#the-scopes-section) Example: ``` catalog: scopes: - code: europe store: 1 locales: - code: fr_FR store: 1 - code: de_DE store: 4 - code: es_ES store: 3 - code: it_IT store: 2 - code: america store: 5 locales: - code: en_US store: 5 - code: en_CA store: 8 - code: fr_CA store: 6 ``` ### The `codes-mapping:` section [](#the-codes-mapping-section) This section is used for the attribute options codes generation. As those codes does not exist in Magento we need to build them based on the default labels. Example: ``` catalog: codes-mapping: - from: '"' to: 'inches' - from: 'â' to: 'a' - from: 'é' to: 'e' - from: 'è' to: 'e' - from: '/' to: '_' ``` ### Health Score 26 — LowBetter than 43% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity7 Limited adoption so far Community8 Small or concentrated contributor base Maturity58 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~6 days Total 4 Last Release 2370d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/144109625f8029112d56f43d08120cf03a0918ea3b4fd59ab53f09b02f630b00?d=identicon)[gplanchat](/maintainers/gplanchat) --- Top Contributors [![gplanchat](https://avatars.githubusercontent.com/u/152367?v=4)](https://github.com/gplanchat "gplanchat (24 commits)") --- Tags akeneoakeneo-installerbundlefixturesmagentomagento-data ### Embed Badge ![Health badge](/badges/kiboko-bisous/health.svg) ``` [![Health](https://phpackages.com/badges/kiboko-bisous/health.svg)](https://phpackages.com/packages/kiboko-bisous) ``` ### Alternatives [shopware/platform The Shopware e-commerce core 3.3k1.5M3](/packages/shopware-platform)[ec-cube/ec-cube EC-CUBE EC open platform. 78527.0k1](/packages/ec-cube-ec-cube)[sylius/sylius E-Commerce platform for PHP, based on Symfony framework. 8.4k5.6M646](/packages/sylius-sylius)[sulu/sulu Core framework that implements the functionality of the Sulu content management system 1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers. 9.0k15.4k](/packages/prestashop-prestashop)[shopware/core Shopware platform is the core for all Shopware ecommerce products. 595.2M385](/packages/shopware-core) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)