kiboko-labs/kloud

Build and manage your development Docker stack for @OroCommerce, OroCRM, OroPlatform and MArello applications

Docker images and stacks for Oro and Marello development

This project aims at building your Docker stack for OroCommerce, OroCRM, OroPlatform and Marello development.

⚠️ Nota: Those stacks are not suited for production hosting, but to provide an environment based on Docker as identical as possible to OroCloud and MarelloCloud on a personal computer.

What to expect from this tool?

This tool has to be used in addition ot the installation instructions from Oro-family applications. It will build an execution environment based on Docker and Docker Compose for your existing projects or can be added to a brand-new project.

Documentation

• Installation of the tool
• Usage in your Oro-family projects
• Frequently Asked Questions
• Docker for Mac optimizations
• Versions sunsetting policy, experimental and discontinued support
• Supported versions and flavors
  • OroPlatform
  • OroCRM
  • OroCommerce
  • Marello
  • Middleware

kloud's Issues

memory_limit=-1

Est-ce que c'est vraiment judicieux? On pourrait pas mettre une valeur assez haute pour être inhabituelle et comme ça détecter les grosses fuites mémoire quand on a du code qui traite des gros volumes et qui mange la ram, parce qu'en l'état, avec le memory_limit = -1 on ne se pose pas la question vu qu'il n'y a pas de limite.

<?php

boucle(4000000); //130mb
boucle(20000000); // 1gb
boucle(100000000); // 4gb

// avec le memory_limit=-1 si le script prends 4gb on ne le détectera pas forcement

function boucle(int $nbLoop)
{
    $test = [];
    for ($i = 0; $i < $nbLoop; $i++) {
        $test[] = $i;
    }
    printMem();
    unset($test);
}

function printMem()
{
    $memBytes = memory_get_usage();
    $memMegaBytes = round($memBytes/1000000);
    $memGigabytes = round($memMegaBytes/1000);
    
    var_dump([
        'bytes'     => $memBytes,
        'megaBytes' => $memMegaBytes,
        'gigaBytes' => $memGigabytes
    ]);
}

Ajout Elastic stack

https://www.elastic.co/fr/elastic-stack

Services non voulus après stack:init

Quand je fais la commande kloud stack:init avec :

• blackfire = non
• xdebug = non

3 services en trop sont créés dans docker-compose.yml qui sont :

• fpm-xdebug
• sh-xdebug
• blackfire

Implement deployment commands

As a developer I want to deploy my application on an environment, should it be local or remote, be able to synchronize the files I have in local and the ones on the remote environment.

Commands to add:

• environment:init Asks questions about the location (server/directory) of the remote environment, environment variables to set and writes them inside a .kloud.environment.yaml file in the local workspace.
• environment:deploy integrates https://deployer.org to deploy the application in the remote environment:
  • rsync the sources
  • build the Docker infrastructure through docker-compose up --no-start
• environment:destroy that integrates https://deployer.org to destroy the application in the remote environment:
  • destroy the Docker infrastructure through docker-compose down and delete the appropriate persistent volumes
  • delete the sources and the directory
• environment:start that integrates https://deployer.org to start the application in the remote environment, should fail if the application wasn't previously deployed
• environment:stop that integrates https://deployer.org to stop the application in the remote environment, should fail if the application wasn't previously deployed
• environemnt:cache:clear that integrates https://deployer.org to clear the application caches and restart the FPM servcie(s)
• environment:rsync that synchronizes the local and remote sources (in case you switched from git branches)
• environment:database:dump that dumps the database in the current state
• environment:database:load that loads a database dump
• environment:variable:get that prints the value of an environment variable
• environment:variable:set that changes the value of an environment variable
• environment:variable:list that prints the values of all environment variables
• environment:variable:unset that unsets an environment variable
• environment:proxy that proxies a port in the stack to a local port (especially for Xdebug and database accesses)
• environment:shell that opens a shell in a node of the execution environment (be it sh, sh-xdebug or sql nodes)

Ajout DBGP

https://xdebug.org/docs/dbgp

Stack upgrade l'input lors de l'installation n'attends pas le choix entre crochets, mais la valeur

Lors du stack upgrade et peut-être du stack init le choix de la version de PHP s'affiche tel que:

`Which PHP version are you using? [7.3]:
[0] 5.6
[1] 7.1
[2] 7.2
[3] 7.3
[4] 7.4
[5] 8.0

`

Pour installer PHP 8.0 il faut tapper 8.0 et non 5 (qui va installer PHP 5). Ce comportement est contre intuitif.

Oro CRM nécéssite PHP 7.4.14

Oro CRM nécessite PHP 7.4.14 et la version de PHP générée est 7.4.12 :

This package requires php ~7.4.14 || ~8.0.0 but your PHP version (7.4.12) does not satisfy that requirement.

Image utilisée:
kiboko/php:7.4-cli-orocrm-ce-4.2-mysql

Limitation max_input_vars

Suite à l'impossibilité de modifier les produits importés par OroAkeneo en BO, nous avons fait une demande à OroInc à ce sujet :
https://magecore.atlassian.net/servicedesk/customer/portal/2/OSD-5122

Voici leur réponse :

Dima Shatovskiy, vendredi 5:31 PM
Hello Xavier,

Your dev environment triggers error because form is not sent to the server completely due to limitation max_input_vars.
default is 1000 but form is very big that is why it doesn't work. Please try to increase limits on dev and you will see it's working.
We would recommend to hide attributes from form that you do not need, it is very inconvenient for use and triggers such fantom errors.

Thank you,
Dima

Ajouter une image php (sh ) avec l'extension pcov

https://github.com/krakjoe/pcov
Nom : sh-pcov
l'image est juste celle de sh + pcov
Il ne faut pas utiliser pcov + blackfire ou xdebug

oro/platform 4.1.4 requires ext-pcntl

Hi,

The php extension ext-pcntl seems to be missing in the following images
kiboko/php:7.3-cli-orocommerce-ce-4.1-mysql
kiboko/php:7.4-cli-orocommerce-ce-4.1-mysql

Got error

Problem 1
  - oro/platform 4.1.4 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system.
  - oro/platform 4.1.4 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system.
  - Installation request for oro/platform 4.1.4 -> satisfiable by oro/platform[4.1.4].

Thanks for your works.

add psql in sh image

The psql utility should be available in the sh image.
Example: ( kiboko/php:7.2-cli-blackfire-orocommerce-ee-3.1-postgresql )
Because some php class , like https://github.com/oroinc/platform/blob/master/src/Oro/Bundle/TestFrameworkBundle/Behat/Isolation/UnixPgsqlIsolator.php

start a psql process in the container