Vagrant Box for Magento 2 Developers

License: MIT License

Shell 100.00%

magento2 devbox developer-tools vagrant virtualbox

magento2-vagrant-for-developers's People

Contributors

Stargazers

Watchers

Forkers

federivo mrtuvn thienphucvx brobie buskamuza refaelgold ronaldocpontes jeffbritts skukla paulerickson ansonliang55 yuriyf arkadiych ufgstores riconeitzel vdloo benmarks nirmalarya spittfree steerjt adrianoaguiar sergi-omit dsikkema-magento warehousesix ameeuw23 vasiliydp wesleywmd nttan moinsam krishnandaiva jatasya bratucornel nofuss jasonheecs valoujjal ariefitriadin nubors chefjuanpi 0820 thaopw changwng spofa lrv lahyani helalbookmark chrislpatton fluidtheory downjse delwar2016 s2010 asurrey viveklucky249-magento2-stuff konstantinzhidkovskiy subratabauri jbelke skaragoez clivewalkden ledian-hymetllari eric-bohanon mikkelson lfolco jamesbong93 rojin-eglobeits mrda oizik leandrofreire08 mauroartizzu hydau nicolaspernot surlymrz nlwstein carlsimpsonmagento scarraban upandfine joomlabeat ravbaba magestar eermolaev beejhuff boooya carlsimpsonfisheye patilswapnilv asimsoroya etaroza nfourteen ygord-vayyar fejal lukepaoloni raybogman 0xh bwebteam shrielenee pdohogne-magento pocketprogrammer yosoyfunes lamaia webdawe northblue salesandorders kirill533

magento2-vagrant-for-developers's Issues

Improve UX of CLI scripts

Options missing from design configuration in backend

Hi,
I followed the instructions and got the store up and running. The problem I'm having is that the only option showing up in the design configuration area is for 'Search Engine Robots', everything else is missing and so I have no way of changing the theme. Any ideas?
Thanks

Upgrade PHP 5.5.9 to PHP 5.6

The latest version of Magento 2 develop branch has a new minimum requirement for PHP version as 5.5.22, so it makes sense to upgrade directly to 5.6.

Enable phpmd and phpcs automatically in PhpStorm

[Docs] Add section to documentation about debugging CLI scripts

The following syntax can be used for that:
php -d xdebug.remote_host=192.168.10.1 -d xdebug.idekey=PHPSTORM -d xdebug.remote_connect_back=0 -d xdebug.remote_autostart=1 bin/magento list

In addition, remote debugging configuration should be created in PhpStorm to listen for incoming connections with provided IDE key.

Add composer parallel install plugin

https://github.com/hirak/prestissimo

If EE is updated with files, no linking will be made

If you use EE and add some new files after m-switch-to-ee, then these files will not be linked to the project. Need to add possibility to re-link EE.

Generate settings.jar for PhpStorm

Generate settings.jar, which contains global PhpStorm settings (some settings are stored in <project_root>/.idea folder, and some are global for all projects). This archive should be compatible with at least the latest version of PHP Storm, and it should be possible to import these settings via File => Import Settings... in PhpStorm.

Unfinished prototype is available in develop-phpstorm-settings branch

Add optional Varnish support

If enabled in config.yaml, varnish 4 must be enabled by default after project initialization (init_project.sh execution).
Ideally it should be possible to change this option, reinstall Magento using m-reinstall and get Varnish enabled/disabled.

It makes sense to create new box with Varnish installed by default (see https://github.com/paliarush/magento2-vagrant-for-developers-packer)

Some hints:

apt-get install apt-transport-https
curl https://repo.varnish-cache.org/GPG-key.txt | apt-key add -
echo "deb https://repo.varnish-cache.org/ubuntu/ trusty varnish-4.1" >> /etc/apt/sources.list.d/varnish-cache.list
apt-get update
apt-get install varnish

Configure as described here http://devdocs.magento.com/guides/v2.0/config-guide/varnish/config-varnish-configure.html

Default config on Ubuntu /etc/default/varnish, change to {{DAEMON_OPTS="-a :80 }}

Remove github token requirement

Github token is not required anymore for avoiding rate limits while downloading composer dependencies.
Github token specification must be made optional and documentation should be updated accordingly (remove step from Installation section and remove Github limitation section)

Problems after vagrant suspend

When doing a vagrant suspend and vagrant up the machine does not return to the same state it was before the suspend. During the vagrant up process I get the errors below which result in a lot of the config files in /etc like the php/mysql/vagrant folders not being created. I am running OS X 10.11.6 but my colleague who is on Windows 10 is not experiencing the same problem so it may be only on Macs or something I have done wrong. I cloned the project in my home folder and my user has admin permissions so I cannot see it being to do with permissions.

==> magento2.vagrant22: cp: 
==> magento2.vagrant22: cannot create regular file ‘/etc/varnish/default.vcl’
==> magento2.vagrant22: : No such file or directory
==> magento2.vagrant22: sed: can't read /etc/php/7.0/cli/conf.d/20-xdebug.ini: No such file or directory
==> magento2.vagrant22: ERROR: 
==> magento2.vagrant22: Module php7.0 does not exist!
==> magento2.vagrant22: sed: can't read /etc/php/7.0/cli/conf.d/20-xdebug.ini: No such file or directory
==> magento2.vagrant22: /tmp/vagrant-shell: line 91: /etc/php/7.0/cli/conf.d/20-xdebug.ini: No such file or directory
==> magento2.vagrant22: /etc/init.d/apache2: 64: .: 
==> magento2.vagrant22: Can't open /etc/apache2/envvars
==> magento2.vagrant22: /etc/init.d/apache2: 76: .: 
==> magento2.vagrant22: Can't open /etc/apache2/envvars
==> magento2.vagrant22: ERROR: APACHE_PID_FILE needs to be defined in /etc/apache2/envvars

I appreciate this could be a vagrant issue but I use vagrant for other things and have never experienced problems when vagrant suspending and vagrant upping.

Does it install magento automatically? question

I don't understand why there is a config.yaml file. Does it run composer install automatically? If yes, I don't see why because most likely you are cloning an already existing project with a database and start making changes... Or am I wrong?

[Windows] m-switch-to-ee with 2gb might be failed during magento installation step

Steps to reproduce:

Set memory to 2048.
Run m-switch-to-ee, wait while files are synchronized, press any key to resume magento installation process.

Expected: Magento EE installed successfully.
Actual: m-switch-to-ee fails with killed process. (not always reproducible)

Workaround: run "vagrant reload"

Make list of shared folders configurable in non-NFS mode

By default, in non-NFS mode (always true for Windows hosts or if NFS is explicitly disabled in config.yaml) the following directories are mounted as VirtualBox shared folders: var/generation and app/etc.

Would be nice to make this list configurable via config.yaml

Magento compiler fails on Windows hosts

Compiler tries to remove var/generation directory, which is mounted as shared folder on Windows hosts, as a result the following error occurs:

magento setup:di:compile The directory "/var/www/magento2ce/var/generation" cannot be deleted Warning!rmdir(/var/www/magento2ce/var/generation): Device or resource busy#0 /var/www/magento2ce/setup/src/Magento/Setup/Console/CompilerPreparation.php(73): Magento\Framework\Filesystem\Driver\File->deleteDirectory('/var/www/magent...')

Until this is fixed, workaround is to comment out the following line in Vagrantfile if you need to run compiler:
config.vm.synced_folder host_magento_dir + '/var/generation', guest_magento_dir + '/var/generation', create: true

The solution might be to use the whole var directory as shared folder instead of var/generation. However need to make sure that performance is not degrading in this case.

scripts throw 'expected binary operator'

Package fabpot/php-cs-fixer is abandoned

Package fabpot/php-cs-fixer is abandoned, you should avoid using it. Use friendsofphp/php-cs-fixer instead.

install npm by default

i try to install npm and gulp at the vagrant machine but i get a lot of issues
there is any why to install it that you recommended?

thanks!

Fix remote debugging for web API functional tests

The problem is that when you run web API functional tests with debugger, it tries to connect to PHPStorm on the host originating the call (guest machine), and obviously fails. Change of remote connect back to static IP in XDebug configuration should help, but need to make sure that it will always work in other cases.

Temporary workaround if you need to run debugging for web API functional tests is:

On the guest (if using PHP 7): vim /etc/php/7.0/cli/conf.d/20-xdebug.ini
Change xdebug.remote_connect_back=1 to xdebug.remote_host=192.168.10.1 (or whatever is your host IP)

Magento version

Hi,

Today at Magento Imagine this github repository has been on multiple slides. I did an installation like described in the readme and everything is working fine. One issue: the default version after installation is v2.0. Magento2 is already on v2.0.4. How can this be fixed?

When updating: i get the message 'We're sorry, no components are available because you cloned the Magento 2 GitHub repository. You must manually update components as discussed in the Installation Guide.' > wouldn't it be better to work with the composer version?

Thanks in advance!

Unable to run init_project.sj

When trying to run the command bash init_project.sh, I receive the following:

installing the 'vagrant-libvirt' plugin. This can take a few minutes...
/usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError)
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:275:in `with_isolated_gem'
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:231:in `internal_install'
        from /usr/lib/ruby/vendor_ruby/vagrant/bundler.rb:102:in `install'
        from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:62:in `block in install_plugin'
        from /usr/lib/ruby/vendor_ruby/vagrant/plugin/manager.rb:72:in `install_plugin'
        from /usr/share/vagrant/plugins/commands/plugin/action/install_gem.rb:37:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/warden.rb:34:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/builder.rb:116:in `call'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `block in run'
        from /usr/lib/ruby/vendor_ruby/vagrant/util/busy.rb:19:in `busy'
        from /usr/lib/ruby/vendor_ruby/vagrant/action/runner.rb:66:in `run'
        from /usr/share/vagrant/plugins/commands/plugin/command/base.rb:14:in `action'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:32:in `block in execute'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `each'
        from /usr/share/vagrant/plugins/commands/plugin/command/install.rb:31:in `execute'
        from /usr/share/vagrant/plugins/commands/plugin/command/root.rb:56:in `execute'
        from /usr/lib/ruby/vendor_ruby/vagrant/cli.rb:42:in `execute'
        from /usr/lib/ruby/vendor_ruby/vagrant/environment.rb:268:in `cli'
        from /usr/bin/vagrant:173:in `<main>'

php version 7.0.5

Hi,

On a fresh install i am getting the below error.
"Magento supports PHP 5.6, 7.0.2, and 7.0.6 or later. Please read Magento System Requirements."

It seems like its installing a php version(7.0.5) thats not compatible with magento 2.1.0

Thanks.

Enable Mail Support

There should be possibility to read Emails sent by Magento. Ideally we should put every email to some directory visible from the host, so it can be opened using host email client (e.g. Outlook).

Is Windows 10 supported?

I got the following error message when I had ran the command bash init_project.sh on Windows10 64bit:

D:/dev/magento2/lib/php/php.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory

$ bash init_project.sh
+ bash /d/dev/magento2/scripts/host/check_requirements.sh
+ '[' -f /d/dev/magento2/lib/php/php.exe ']'
+ php_executable=php
+ echo php
+ php -v
/d/dev/magento2/scripts/host/check_requirements.sh: line 9: php: command not found
+ grep -q Copyright
+ bash /d/dev/magento2/scripts/host/install_php.sh
+ [[ Windows == \W\i\n\d\o\w\s ]]
+ curl http://windows.php.net/downloads/releases/archives/php-5.6.9-nts-Win32-VC11-x86.zip -o /d/dev/magento2/lib/php.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 20.1M  100 20.1M    0     0  2802k      0  0:00:07  0:00:07 --:--:-- 3308k
+ unzip -q /d/dev/magento2/lib/php.zip -d /d/dev/magento2/lib/php
+ rm -f /d/dev/magento2/lib/php.zip
+ cp /d/dev/magento2/lib/php/php.ini-development /d/dev/magento2/lib/php/php.ini
+ sed -i.back 's|; extension_dir = "ext"|extension_dir = "ext"|g' /d/dev/magento2/lib/php/php.ini
+ sed -i.back 's|;extension=php_openssl.dll|extension=php_openssl.dll|g' /d/dev/magento2/lib/php/php.ini
+ rm -rf /d/dev/magento2/lib/php/php.ini.back
++ bash /d/dev/magento2/scripts/host/get_path_to_php.sh
+ '[' -f /d/dev/magento2/lib/php/php.exe ']'
+ php_executable=/d/dev/magento2/lib/php/php
+ echo /d/dev/magento2/lib/php/php
+ php_executable=/d/dev/magento2/lib/php/php
+ /d/dev/magento2/lib/php/php -v
+ grep -q Copyright
D:/dev/magento2/lib/php/php.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
+ set +x
Automatic PHP installation is not available for your host OS. Please install any version of PHP to allow Magento dependencies management using Composer. Check out http://php.net/manual/en/install.php

Sample data for CE

Hi,

is it me, or is sample data not working currently? The default config.yaml file seems to have filled out defaults for the CE edition with sample data (only thing NOT set is the "install_sample_data" option).

Regardless of the "install_sample_data" option, the sample data isn't installed. If I attempt to deploy it manually using "bash m-bin-magento sample:deploy" (which seems it shouldn't be needed, but regardless) it fails with the following:

$ bash m-bin-magento sample:deploy
+ arguments=sample:deploy
+ cd /d/magento/vagrant-magento
+ vagrant ssh -c '$MAGENTO_ROOT/bin/magento sample:deploy'
<warning>You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug</warning>
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package magento/module-sales-rule-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 2
    - The requested package magento/module-cms-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 3
    - The requested package magento/module-bundle-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 4
    - The requested package magento/module-grouped-product-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 5
    - The requested package magento/module-swatches-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 6
    - The requested package magento/module-wishlist-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 7
    - The requested package magento/module-downloadable-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 8
    - The requested package magento/module-tax-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 9
    - The requested package magento/module-catalog-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 10
    - The requested package magento/module-review-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 11
    - The requested package magento/module-offline-shipping-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 12
    - The requested package magento/module-sales-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 13
    - The requested package magento/module-widget-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 14
    - The requested package magento/module-msrp-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 15
    - The requested package magento/module-theme-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 16
    - The requested package magento/module-configurable-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 17
    - The requested package magento/module-product-links-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 18
    - The requested package magento/sample-data-media could not be found in any version, there may be a typo in the package name.
  Problem 19
    - The requested package magento/module-customer-sample-data could not be found in any version, there may be a typo in the package name.
  Problem 20
    - The requested package magento/module-catalog-rule-sample-data could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.
There is an error during sample data deployment. Composer file will be reverted.

I'm assuuming this is caused by some disparity between the used Magento2 and sample data GIT, but I'm unsure how to resolve it.

Only see app and etc directory

I'm on windows 10 and get all the way through the installation, but when I launch in browser I just see the app directory and in that only the etc directory. Any idea what I could be doing wrong?

No field for amqp-virtualhost

Need to add option to m-reinstall script for amqp-virtualhost.

SSH hanging

I have tried everything, I'm must be missing something silly. Thanks for any help

An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating

debug info

DEBUG virtualbox_5_1:   - [1, "tcp3248", 3248, 22]
DEBUG ssh: Checking key permissions: /home/crantron/.vagrant.d/insecure_private_key
 INFO ssh: Attempting SSH connection...
 INFO ssh: Attempting to connect to SSH...
 INFO ssh:   - Host: 127.0.0.1
 INFO ssh:   - Port: 3248
 INFO ssh:   - Username: vagrant
 INFO ssh:   - Password? false
 INFO ssh:   - Key Path: ["/home/crantron/.vagrant.d/insecure_private_key"]
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2016-08-10T14:12:04.645705 #17569] DEBUG -- net.ssh.transport.session[12087e8]: establishing connection to 127.0.0.1:3248
D, [2016-08-10T14:12:04.646156 #17569] DEBUG -- net.ssh.transport.session[12087e8]: connection established
I, [2016-08-10T14:12:04.646251 #17569]  INFO -- net.ssh.transport.server_version[1205d90]: negotiating protocol version

DEBUG ssh: == Net-SSH connection debug-level log END ==
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000002487d10>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000205a468>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000217a690>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000000021b0308>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000000021b0380>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Released process lock: machine-action-b595c2c50a1b63fb337385be82677372
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000000023f59b0>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::NetSSHException: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating>
ERROR vagrant: An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
ERROR vagrant: /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/ssh/communicator.rb:429:in `rescue in connect'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/ssh/communicator.rb:349:in `connect'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/ssh/communicator.rb:209:in `execute'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/ssh/communicator.rb:246:in `sudo'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:69:in `block (2 levels) in provision_ssh'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:60:in `tap'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:60:in `block in provision_ssh'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:220:in `with_script_file'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:58:in `provision_ssh'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/provisioners/shell/provisioner.rb:24:in `provision'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:133:in `run_provisioner'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/environment.rb:473:in `hook'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:121:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:121:in `block in call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:103:in `each'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:103:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/box_check_outdated.rb:78:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:225:in `action_raw'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:200:in `block in action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/environment.rb:561:in `lock'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:186:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:186:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
 INFO interface: error: An error occurred in the underlying SSH library that Vagrant uses.

Add Solr support (EE only)

Automate remote interpreter configuration

The following step should be automated and performed in scope of init_project.sh:

Configure remote PHP interpreter in PHP Storm. Go to Settings => Languages & Frameworks => PHP, add new remote interpreter and select "Deployment configuration" as a source for connection details.

Current issue seems to depend on Generate settings.jar for PhpStorm

How to connect mysql on windows via Navicat?

all path variables missing quotes

which leads to heavy issues with spaces in root paths

Add help documentation to configure phpunit in windows

I'm trying to configure phpunit in phpstorm and I get errors. I think it would be wonderful to have documentation on how to configure phpunit in windows.

Tried to follow:

When I "play" phpunit, i get this:

vagrant://C:\Users\Jordi\vagrant-magento/usr/bin/php /home/vagrant/.phpstorm_helpers/phpunit.php --configuration /vagrant/magento2ce/dev/tests/unit/phpunit.xml.dist
Testing started at 10:58 ...
bash: line 0: cd: /vagrant/magento2ce/dev/tests/unit: No such file or directory
Could not read "/vagrant/magento2ce/dev/tests/unit/phpunit.xml.dist".

My configuration:

Support Magento installation from Composer packages

Current workaround is to populate <vagrant_project_root>/magento2ce using the similar command before running init_project.sh:

composer create-project magento/project-enterprise-edition=2.1.0-rc2 --repository-url=https://repo.magento.com --ignore-platform-reqs

Invalid link provided in [optional instruction]

Since master branch is unavailable, link provided in the end of optional instructions is invalid:

Use instructions provided here https://github.com/paliarush/vagrant-magento/blob/master/docs/phpstorm-configuration-windows-hosts.md

Issue location:
https://github.com/paliarush/magento2-vagrant-for-developers/blob/1693ee7d14a52335fc75bdb15750601d037df088/scripts/guest/m-reinstall

Application very slow, VagrantFile settings, Magento app permissions error

Per instructions document adding the following code to VagrantFile:

Vagrant.configure(2) do |config| config.vm.synced_folder '../magento2ce/var', '/var/www/magento2ce/var' config.vm.synced_folder '../magento2ce/app/etc', '/var/www/magento2ce/app/etc' end

...causes this error:

If I take out the code and vagrant reload the application runs but has very slow page load times (1-2 minutes).

Why would this code cause a permissions error?

I'm running on Win7, downloaded Magento code via Composer and have EE edition inside "magento2ce" folder.

Add Magento Sample Data Support

It should be possible to specify sample data repository in config.yaml. New script should be introduced (e.g. m-reinstall-with-sample-data) and it should link sample data directories, invoke m-reinstall and then unlink sample data directories.

When you switch between CE and EE, or invoke m-reinstall there must be no sample data installed.

Fix must be backward compatible.

chmod: cannot access ‘bin/magento’: No such file or directory

Hi there,

During the installation (presumably at the part where it tries to install Magento) I am getting the following error:

+ sudo chmod +x bin/magento
chmod: cannot access ‘bin/magento’: No such file or directory

Please could you advise where im going wrong?

init-project.sh failing when in directory structure with spaces

Put you project into /Volumes//My Vagrant Machines/ and let the init-project.sh run.

Add Redis Support

Enable Redis for session (with configurable fields). Changes should be applicable after "vagrant reload".
http://devdocs.magento.com/guides/v2.0/config-guide/redis/redis-session.html
Enable Redis for FPC (with configurable fields). Changes should be applicable after "vagrant reload".
http://devdocs.magento.com/guides/v2.0/config-guide/redis/redis-pg-cache.html

Cannot switch to EE using bash m-switch-to-ee

I'm downloading EE from a private repo. Here's what the repo section of my config.yaml looks like.

repository_url:
  # [To apply changes: init-project -fc]
  ce: "https://github.com/magento/magento2.git "
  ee: "https://github.com/LCind/magento2ee.git"

From my host machine, executing bash m-switch-to-ee returns the following:

C:\Projects\vagrant-magento>bash m-switch-to-ee
+ [[ -f /c/Projects/vagrant-magento/lib/php/php.exe ]]
+ php_executable=php
+ echo php
+ [[ ! -f /c/Projects/vagrant-magento/magento2ce/magento2ee/app/etc/aliases_to_classes_map.json ]]
+ set +x
EE codebase is not available

adding misc extensions befor installing sample data

I'd like to install some other extensions with the init_project.sh (via composer).
But they have to be installed before the sample data.
How can I handle this?

Install EE by default, if EE repository is specified

Cannot edit product from sample data

I have install CE version with sample data by m-switch-to-ce -f.

Now I'm trying to edit selected product. Product name 'Driven Backpack'.
I've changed activity category for this product, clicked Save and got:

Item (Magento\Framework\DataObject) with the same ID "16" already exists.

What am I doing wrong? Don't know how to edit product or edit of random data is impossible?

Add swapfile to use less physical memory

If we need to install magento EE and run tests, then about 3GB of memory should be allocated.
I propose to add swapfile to guest machine and add ability to configure size of swapfile ("0" means no swapfile).
Would be nice if swapfile settings could be applied after "vagrant reload"

Add ElasticSearch support (EE only)

Add Timezones Suport

Timezones should be configurable via config.yaml and have default values. Changes should be applicable after "vagrant reload".
Add a shell script to show timezones "all in one" including all Magento config timezones(all scopes) . Should show timezone in UTC, name of timezone, difference with default Magento timezone.
Next timezones should be supported:

php timezone;
db timezone;
web server timezone;
default Magento timezone;

Cannot switch to EE

The config.yaml file shows the correct path to the magento2ee folder. Upon running:

bash init_project.sh -c

I still get the message that the EE codebase is not available.

Make guest configs editable from IDE

Would be really convenient to edit guest configs directly from IDE, e.g. PHP, Apache, MySql, Varnish, hosts etc.

Create default configuration for tests

init_project.sh should configure PhpStorm so that Unit, Integration, Web API tests run configuration are available by default after project initialization.

paliarush / magento2-vagrant-for-developers Goto Github PK

magento2-vagrant-for-developers's People

Contributors

Stargazers

Watchers

Forkers

magento2-vagrant-for-developers's Issues

Recommend Projects

Recommend Topics

Recommend Org