magento2-fast-vm

Fix issue on elasticsearch installation (version was missing during installation process)

Compatibility support for Magento 2.4.6

• include 2FA deactivation as an installation option https://github.com/markshust/magento2-module-disabletwofactorauth
• add support for php8.2
• add support for opensearch 2.5
• add support for elasticsearch 8.0
• add global support for magento 2.4.6 and keep retrocompatibility with older versions
• 2 new config lines arguments were added in config.yaml :
  • search_engine
  • disable_two_factor_auth

Notes

Config lines added are mandatory, you must update your config.yml consequently

• [#108] set "allow-plugins" option in composer install script (to fix existing composer.json)
  (related topic: https://magento.stackexchange.com/questions/352353/why-composer-install-is-asking-to-allow-plugins)

• [#105] due to kernel upgrade, grub installation was invalid : to resolve it, we uninstall grub before kernel update.

• Validate 2.4.5 Magento installation
• Replace Mailcatcher by Mailhog

• Adapt debconf-set-selections for Mysql 5.7
• Fix installation on system =<2.4.2
• Validate installation on Magento release 2.3 and 2.4

• Resolving issue #101
• Fix path for php-fpm
• Fix path for mysql cnf
• Resolve issue with mailcatcher installation
• Remove redis custom configuration

• Add support for php version 8.1 when magento version is equal or greater than 2.4.4, php 8.1 will be installed by default
• Add support for composer v2 on Magento version compatible (>=2.4.2)
• Remove opcache config breaking 2.4.4 installation due to php-8.1 (native opcache, jit etc...)
• Set default installation to version 2.4.4
• Prepare provisionner for migration to debian 11
• Update readme.md

• improve mysql script for import

• Resolve issue on git project install with nginx configuration
• Make sur env.php and config.php are deleted before install
• Add php socket extension for enterprise edition >=2.4.0

• Resolve issue on apt-get install, sometimes it could be stuck on re-installation: we now delete apt list repository on provision.
• Fix elasticsearch v7.x installation, now provided on version >= 2.4.0 and fallback to v6.x for lower version.
• Adding MySQL 8 with Percona for version >= 2.4.0 and fallback to 5.7 for lower version.
• Composer v1 could be stuck on installation, COMPOSER_MEMORY_LIMIT=-1 has been set to avoid this.
• Sample data installation has been reworked to follow documentation, it may not work properly on Magento version <= 2.2.x (not tested).
• Rsync mount now required to run vagrant reload to enable the watcher on first installation (this is not required on next vagrant up).
• Resolve issue #79: magento requires correct permission to add image on catalog product from back-office: global permissions are no more forced with bindfs, we only force the user group (www-data) in order to make it work properly with nginx.
• Update config.yaml.example to Magento v2.4.2

• Resolve issue #73 by locking composer version to v1.x

• Resolve issue #71 to allow elasticsearch service to always restart
• Add comment under section "Issues" of README.md for issue #70

Upgrade this developer box to install Magento latest release 2.4.0.

• Add php version to 7.4 when magento version is equal or greater than 2.3.5-p2
• Add repository and installation for elasticsearch7.X and apply it by default (elasticsearch6 is now deprecated)

• Set command non-interactive to resolve issue while settings redis configuration in post-install script.
• Move php settings to system-env.sh to avoid issue while running provisionners separately

On version 2.3.5 some sample pages trigger 502 errors.
According to logs: "upstream sent too big header while reading response header from upstream".
Resolved by increasing default fastcgi_buffers.

• Increase default fastcgi buffers:
  fastcgi_buffers 16 14k;
  fastcgi_buffer_size 32k;
• Update config.yaml.example: magento v2.3.5

• Resolve package installation dependency #50
• Update config.yaml.example: magento v2.3.4

• Add Elasticsearch 6

• Replace Mariadb by Percona, according to optimal configuration from Magento doc:
  https://devdocs.magento.com/guides/v2.3/extension-dev-guide/build/optimal-dev-environment.html#optimal-configuration

• Add php version 7.3 according to last dependency from magento 2.3.3

• Add database import from compressed dump, crypted_key is also available in config.yaml to avoid any issue with encrypted values with imported data

• Replaced apache by nginx/php-fpm to improve performance

• Find out a solution according to https://github.com/winnfsd/vagrant-winnfsd/issues/104
  Windows user just have to run: Add-MpPreference -ExclusionProcess winnfsd.exe as admin in powershell and this will definitly solve issue with NFS and malformated composer autoload

• Magento user is no longer necessary, project is now fully accessible through default vagrant user

• Project path has been moved from /srv/magento to /home/vagrant/magento

• Rsync mount is now available in order to reach better performance

• Add php version in config.yaml to allow user to override the default version installed

• Fix unix mode for extra shell provision

• Magento setup has been adapted to be compatible with magento 2.1.X (related issue #16)

• Default php version is now correctly set to 7.0 for M2.0.x & M2.1.x