Simple Magento 2 Vagrant Box

Overview

Magento2 Vagrant Box

A simple way to get magento2 up and running. It consists of a Debian Wheezy box provised via Puppet. The provider is Virtual Box. It will install apache2 +fastcgi, php, php-fpm, mysql and any other necessary dependancies.

The Magento 2 repository is a git submodule and can be edited/explored from the host machine. It is accessed by the guest via shared directories.

Usage

Installation

  1. Clone this repository: git clone --recursive https://github.com/rgranadino/mage2_vagrant.git
  2. Navigate into the repository via cd
  3. IMPORTANT: If you cloned the repository without the --recursive param, you need to initialize the required submodules: git submodule update --init --recursive
  4. Start up virtual machine: vagrant up
  5. Point a host name to 192.168.56.10 in /etc/hosts echo '192.168.56.10 mage2.dev' >> /etc/hosts

NOTE: Some composer dependancies require git. Agent Forwarding over SSH is enabled in the Vagrant file but you must have ssh-agent running and your key added. Running ssh-add should add the default key to the identities list, which presumably is the same key used to access github/bitbucket. You'll may also need to create a API access token in github, instructions can be found here:

  1. Once the machine completes provisioning, SSH to the server (vagrant ssh).
  2. Add your Magento Connect authentication credentials to the global composer auth.json:
  • Open or create the file ~/.composer/auth.json
  • Add the Magento Connect authentication credentials (if you don't have any, please check here on how to create them):
{
    "http-basic": {
        "repo.magento.com": {
            "username": "<public key>",
            "password": "<private key>"
        }
    }
}
  • Or you can use the composer config command: composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
  1. Install Magento 2 by running:
  • Via CLI (recommended)

    • reinstall (Magento without sample data) or reinstall -s (Magento with sample data).
  • Via Web Installer

    • Please go to the Magento directory within the vagrant box (cd /vagrant/data/magento2/) and run composer install. Then open 'http://mage2.dev/setup' in your browser and go through the installation process.

Updating

  1. From the host machine run git pull && git submodule update --init && vagrant provision.
  • If there is an update to the manifests/mage.pp or files/* files it is recommended to provision the guest machine. This can be done by running: vagrant provision. There is also a cron that runs every 15 minutes to provision within the guest machine in the event it's not done after updating.
  1. If you want to start from a clean slate run: reinstall from within the guest machine. This will uninstall the application and reinstall it from scratch.

Shell Aliases / Scripts

  • m - cd into the base magento directory: /vagrant/data/magento2
  • reinstall - run magento shell uninstall script with the cleanup_database flag and run installation again, uses http://mage2.dev as base URL
  • reinstall -s - install magento with sample data
  • mt - run bulk magento test suites

Status and Debug utilities

A status vhost on port 88 has been setup to view apache's server status, php-fpm status as well as some other utilities.

Magento Admin User

  • Username: admin
  • Password: password123

Database Info

  • Username: root
  • Password: mage2
  • DB Name: mage2

SSH Info

  • username: vagrant
  • password: vagrant

It's also possible to use vagrant ssh from within the project directory

File Structure

Host Machine / Project directory

  • manifests/mage.pp - Puppet manifest file
  • files/ - contains various service configuration files
    • bash_aliases - vagrant user bash aliases script
    • fastcgi.conf - fastcgi configuration
    • reinstall.sh - magento reinstall wrapper script
    • site.conf - apache virtual host configuration
    • www.conf - php-fpm pool configuration
    • xdebug.ini - php xdebug configuration file
  • data/magento2 - Git submodule to Magento2 Github repository: https://github.com/magento/magento2
  • data/magento2-sample-data - Git submodule to Magento2 Sample Data Github repository: https://github.com/magento/magento2-sample-data

Guest Machine

  • /vagrant/data/magento2 - Apache Document Root
Comments
  • Extremely slow

    Extremely slow

    Loading the frontend is taking (with demo data) over 10 seconds. Also seems to not load/render page using correct css. no 404's that i can find.

    Admin is responding quickly.... Not sure what has caused this.

    opened by encodes 7
  • Please Update Your Database - Error

    Please Update Your Database - Error

    Hi,

    I am trying to get this set up, I am on Mac OSX 10.10.1, and this is the error I am getting when I visit mage2.dev

    Please update your database: Run "php –f index.php update" from the Magento root/setup directory.
    The following modules are outdated:
    Magento_Store schema: current version - 2.0.0.0, required version - 2.0.0
    Magento_Store data: current version - 2.0.0.0, required version - 2.0.0
    Magento_Cms schema: current version - 2.0.0.1, required version - 2.0.0
    Magento_Cms data: current version - 2.0.0.1, required version - 2.0.0
    Magento_AdminNotification schema: current version - 2.0.0.0, required version - 2.0.0
    Magento_AdminNotification data: current version - 2.0.0.0, required version - 2.0.0
    #0 [internal function]: Magento\Framework\Module\Plugin\DbStatusValidator->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
    #1 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(62): call_user_func_array(Array, Array)
    #2 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(57): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')
    #3 /vagrant/data/magento2/app/code/Magento/PageCache/Model/App/FrontController/VarnishPlugin.php(53): Magento\Framework\Interception\Chain\Chain->Magento\Framework\Interception\Chain\{closure}(Object(Magento\Framework\App\Request\Http))
    #4 [internal function]: Magento\PageCache\Model\App\FrontController\VarnishPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
    #5 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(62): call_user_func_array(Array, Array)
    #6 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(90): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')
    #7 /vagrant/data/magento2/app/code/Magento/PageCache/Model/App/FrontController/BuiltinPlugin.php(71): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\App\FrontController\{closure}(Object(Magento\Framework\App\Request\Http))
    #8 [internal function]: Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
    #9 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(95): call_user_func_array(Array, Array)
    #10 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(119): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)
    #11 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Http.php(114): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
    #12 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(244): Magento\Framework\App\Http->launch()
    #13 /vagrant/data/magento2/index.php(38): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http))
    #14 {main}
    

    I went into /setup/ and ran php -f index.php update and it ran through the list with no errors, but this error message continues to stay up.

    Any ideas?

    opened by drewrawitz 5
  • Dropbox host returning 509

    Dropbox host returning 509

    In your Vagrantfile, you've set the Debian box URL to a Dropbox location. This is (at least currently) returning a '509 Bandwidth error'

    Are there any other places this can be sourced from? Thanks!

    opened by Morgon 5
  • Installation Exception - 'Area code is not set' in

    Installation Exception - 'Area code is not set' in

    I am trying to install Magento2 by using command line.

    I did execute this command reinstall -s

    I am getting following exception and can not install sample data.

    Please help me to fix this issue.

    [SUCCESS]: Magento installation complete. /vagrant/data/magento2 Installing sample data... ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Nothing to install or update Generating autoload files exception 'Magento\Framework\Exception\LocalizedException' with message 'Area code is not set' in /vagrant/data/magento2/lib/internal/Magento/Framework/App/State.php:154 Stack trace: #0 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(173): Magento\Framework\App\State->getAreaCode() #1 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(130): Magento\Framework\Session\SessionManager->start() #2 /vagrant/data/magento2/app/code/Magento/Backend/Model/Auth/Session.php(98): Magento\Framework\Session\SessionManager->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State)) #3 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(148): Magento\Backend\Model\Auth\Session->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State), Object(Magento\Framework\Acl\Builder\Proxy), Object(Magento\Backend\Model\Url), Object(Magento\Backend\App\Config)) #4 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(91): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Magento\Backend...', Array) #5 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Backend...') #6 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Backend...') #7 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Backend...', NULL, 'session', 'Magento\Tools\S...') #8 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array) #9 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...') #10 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Tools\S...') #11 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Tools\S...', NULL, 'installer', 'Magento\Tools\S...') #12 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array) #13 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...', Array) #14 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(220): Magento\Framework\ObjectManager\ObjectManager->create('Magento\Tools\S...', Array) #15 /vagrant/data/magento2/dev/tools/Magento/Tools/SampleData/install.php(29): Magento\Framework\App\Bootstrap->createApplication('Magento\Tools\S...', Array) #16 {main}

    Next exception 'Magento\Framework\Exception\SessionException' with message 'Area code not set: Area code must be set before starting a session.' in /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php:175 Stack trace: #0 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(130): Magento\Framework\Session\SessionManager->start() #1 /vagrant/data/magento2/app/code/Magento/Backend/Model/Auth/Session.php(98): Magento\Framework\Session\SessionManager->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State)) #2 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(148): Magento\Backend\Model\Auth\Session->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State), Object(Magento\Framework\Acl\Builder\Proxy), Object(Magento\Backend\Model\Url), Object(Magento\Backend\App\Config)) #3 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(91): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Magento\Backend...', Array) #4 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Backend...') #5 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Backend...') #6 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Backend...', NULL, 'session', 'Magento\Tools\S...') #7 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array) #8 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...') #9 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Tools\S...') #10 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Tools\S...', NULL, 'installer', 'Magento\Tools\S...') #11 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array) #12 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...', Array) #13 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(220): Magento\Framework\ObjectManager\ObjectManager->create('Magento\Tools\S...', Array) #14 /vagrant/data/magento2/dev/tools/Magento/Tools/SampleData/install.php(29): Magento\Framework\App\Bootstrap->createApplication('Magento\Tools\S...', Array) #15 {main}vagrant@mage2:/vagrant/data/magento2$ clear

    vagrant@mage2:/vagrant/data/magento2$ clear

    opened by ghost 4
  • Sample data installation no longer works

    Sample data installation no longer works

    The method of installing the sample data has changed. It no longer works as with Magento 1. It first has to be added as a composer dependency, and after the package is installed an install script needs to be executed

    composer config repositories.magento composer http://packages.magento.com
    composer require magento/sample-data:0.42.0-beta6 magento/sample-data-media:0.42.0-beta1 --dev
    php -f dev/tools/Magento/Tools/SampleData/install.php -- --admin_username=admin
    

    More information: http://devdocs.magento.com/guides/v1.0/install-gde/install/sample-data.html

    opened by Vinai 4
  • Can not work on my windows 8.1 Oracle VirtualBox.

    Can not work on my windows 8.1 Oracle VirtualBox.

    I follow the read.me file, but when I use the url 'http://mage2.dev' on my browser. I got the error message: The webpage is not available. I got the same error when I type the following urls on my browser: http://mage2.dev:88/server-status, http://mage2.dev:88/fpm-status.

    Please elaborate the install environment. I got nothing output to the prompt window when I type 'git submodule update --init' from my git bash.

    opened by tshuy 4
  • vagrant up needs password

    vagrant up needs password

    i'm trying to run vagrant up but it keeps asking me for admin password at:

    Exporting NFS shared folders... ==> default: Preparing to edit /etc/exports. Administrator privileges will be required... Password:

    None of the passwords in the readme works here...

    opened by MaxHill 3
  • host does not work

    host does not work

    After install and vagrant up Can not open hosts "192.168.56.10 mage2.dev" on browser. /etc/hosts file was effected Ssh working fine.

    In install I get error ==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev ==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

    I do not know if it depend to problem. Please advise I try in win7 and ios system

    opened by kostya7777 3
  • Update to Magento 2 stable release

    Update to Magento 2 stable release

    Thanks for jumping right on the M2 stable release. Tried to update the box today, but something went wrong. I went to the dir I cloned this repo on my Mac and ran:

    git pull && git submodule update --init && vagrant provision
    

    This is the output I got back:

    remote: Counting objects: 16, done.
    remote: Compressing objects: 100% (3/3), done.
    remote: Total 16 (delta 5), reused 5 (delta 5), pack-reused 8
    Unpacking objects: 100% (16/16), done.
    From github.com:rgranadino/mage2_vagrant
       97f2355..a8d69b7  master     -> origin/master
    Fetching submodule data/magento2
    remote: Counting objects: 121899, done.
    remote: Compressing objects: 100% (2874/2874), done.
    remote: Total 121899 (delta 46358), reused 44573 (delta 44573), pack-reused 74010
    Receiving objects: 100% (121899/121899), 17.84 MiB | 1.75 MiB/s, done.
    Resolving deltas: 100% (74485/74485), completed with 8198 local objects.
    From https://github.com/magento/magento2
       c077da6..4cae5d0  develop    -> origin/develop
       9d4c58e..4cae5d0  master     -> origin/master
     * [new branch]      merchant_beta -> origin/merchant_beta
     * [new tag]         2.0.0      -> 2.0.0
     * [new tag]         1.0.0-beta2 -> 1.0.0-beta2
     * [new tag]         1.0.0-beta3 -> 1.0.0-beta3
     * [new tag]         1.0.0-beta4 -> 1.0.0-beta4
     * [new tag]         1.0.0-beta5 -> 1.0.0-beta5
     * [new tag]         1.0.0-beta6 -> 1.0.0-beta6
     * [new tag]         2.0.0-rc   -> 2.0.0-rc
     * [new tag]         2.0.0-rc2  -> 2.0.0-rc2
    Updating 97f2355..a8d69b7
    Fast-forward
     .gitmodules               |  3 +++
     README.md                 | 15 +++++++++++----
     Vagrantfile               |  5 ++---
     data/magento2             |  2 +-
     data/magento2-sample-data |  1 +
     files/reinstall.sh        | 14 +++++---------
     6 files changed, 23 insertions(+), 17 deletions(-)
     create mode 160000 data/magento2-sample-data
    Submodule 'data/magento2-sample-data' (https://github.com/magento/magento2-sample-data.git) registered for path 'data/magento2-sample-data'
    error: Your local changes to the following files would be overwritten by checkout:
        composer.json
        composer.lock
    Please, commit your changes or stash them before you can switch branches.
    error: The following untracked working tree files would be overwritten by checkout:
        app/code/Magento/SampleData/README.md
        app/code/Magento/SampleData/composer.json
        app/code/Magento/SampleData/etc/di.xml
        app/code/Magento/SampleData/etc/module.xml
    Please move or remove them before you can switch branches.
    Aborting
    Cloning into 'data/magento2-sample-data'...
    remote: Counting objects: 4771, done.
    remote: Compressing objects: 100% (171/171), done.
    remote: Total 4771 (delta 96), reused 0 (delta 0), pack-reused 4579
    Receiving objects: 100% (4771/4771), 77.37 MiB | 1.07 MiB/s, done.
    Resolving deltas: 100% (1560/1560), done.
    Checking connectivity... done.
    Submodule path 'data/magento2-sample-data': checked out '4987f3fbde8279b9366a859b760cad13e89a9354'
    Unable to checkout '4cae5d058b7ad877b2ec7d2b6fa0a500f7c16860' in submodule path 'data/magento2'
    

    There are no loose files in my working directory for this repo, but I'm a little hazy how git submodules work and fit into all this. This ENV was setup with sample data before.

    opened by brendanfalkowski 3
  • Puppet fails on install (vagrant up)

    Puppet fails on install (vagrant up)

    ssh-agent is running on my host machine, github is using the correct key. Still the intial vagrant up fails with the error below. Am I missing something?

    ==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
    ==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
    The SSH command responded with a non-zero exit status. Vagrant
    assumes that this means the command failed. The output for this command
    should be in the log above. Please read the output to determine what
    went wrong.
    
    opened by DrOctogon 3
  • error during install (Step 6) and successful fix

    error during install (Step 6) and successful fix

    Thanks for your very clear readme file @rgranadino ! This is my first vagrant install outside of work. So here's the deal: Everything worked just fine until I did the Magento install process, and according to the console.log below the progress bar ( at mage2.dev/install ), We failed during catalog products installation. There was an error but I don't recall the exact wording. At this point I didn't think to try pressing the "Try Again" button at the top.

    Oh, and also the "install sample data" checkbox was grayed out (I remember getting a sick feeling that something was going to go wrong...)

    Then I found this video: https://www.youtube.com/watch?v=d_31MyPT1YI - and go to 11:21 on the time

    You'll see he's adding "magento/sample-data" and "magento/sample-data-media" in the require portion of composer.json. So I did that in your composer.json file as well.

    Ran the entire process from scratch just to be sure, and this time:

    1. I still got a halt in the progress bar at Installing catalog data at about 67%, but with no error message
    2. I then had the bright idea to try the "Try again" button. This got me to like 96% and it stopped with "Installing catalog search" and stopped again
    3. One more click of the "Try Again" button and it was successfully installed.

    Perhaps adding these two sample-data required lines will be helpful, but the Readme should also mention the "Try Again" button. Typical Magento ;) ..

    opened by samfullman 3
  • symlink Protocol Error

    symlink Protocol Error

    My VBox is in windows 10 and I got this error Cannot create a symlink for "/vagrant/data/magento2/app/design/frontend/Magento/luma/web/images/logo.svg" and place it to "/vagrant/data/magento2/pub/static/frontend/Magento/luma/en_US/images/logo.svg" Warning!symlink(): Protocol error

    do you have some idea ? I already add on Vagrantfile vb.customize ['setextradata', :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate//vagrant", '1']

    opened by Jerome-Fraissinet 1
  • Update php version

    Update php version

    Getting a php error when trying to update magento to 2.1.7. How do you update php version?

    vagrant@mage2:/vagrant/data/magento2$ composer require magento/product-community-edition 2.1.7 --no-update ./composer.json has been updated vagrant@mage2:/vagrant/data/magento2$ composer update 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/product-enterprise-edition could not be found in any version, there may be a typo in the package name. Problem 2 - Installation request for magento/product-community-edition 2.1.7 -> satisfiable by magento/product-community-edition[2.1.7]. - magento/product-community-edition 2.1.7 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (5.5.38) does not satisfy that requirement.

    Potential causes:

    Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems. vagrant@mage2:/vagrant/data/magento2$

    opened by frshjb373 0
  • Installation get stuck on 65%

    Installation get stuck on 65%

    All seemed to work fine untill I got to the installation step, what did I missed ? Anyways steps to reproduce:

    1. cloned the repo with the --recursive flag as explained

    2. cd into that directory and ran vagrant up

    3. added a record to windows/system32/drivers/etc/hosts (in my case dev.magento.com) to point to the vagrant IP address

    4. ssh'ed into the machine and created the file ~/.composer/auth.json with the "http-basic" configurations that was asked and entered my public and private keys.

    5. had some issues running the reinstall command so I've looked in issues and someone already found a walk around so I've used it and changed the file format to unix: #58

    6. ran the reinstall with the flag -s to have some sample data which started composer installation: 6

    something seems to went wrong here or its just an unimportant notice message of composer, see picture below: 7

    1. logged into my database after the installation table seems still to be empty, perhaps it is expected results or something went wrong durring the reinstall command/composer install.

    2. lastly went to the browser and walked through the setup steps, on the 65% it always get stuck. I've tried it 2 times, without any success: 5

    opened by edenreich 1
  • VBox Guest Additions

    VBox Guest Additions

    I get this error after vagrant up:

    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box 'mage2_dev'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: mage2_vagrant_default_1490177510475_12013
    ==> default: Fixed port collision for 22 => 2222. Now on port 2200.
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
        default: Adapter 1: nat
        default: Adapter 2: hostonly
    ==> default: Forwarding ports...
        default: 22 (guest) => 2200 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
        default: SSH address: 127.0.0.1:2200
        default: SSH username: vagrant
        default: SSH auth method: private key
        default:
        default: Vagrant insecure key detected. Vagrant will automatically replace
        default: this with a newly generated keypair for better security.
        default:
        default: Inserting generated public key within guest...
        default: Removing insecure key from the guest if it's present...
        default: Key inserted! Disconnecting and reconnecting using new SSH key...
    ==> default: Machine booted and ready!
    [default] GuestAdditions versions on your host (5.1.16) and guest (4.1.18) do not match.
    Reading package lists...
    Building dependency tree...
    Reading state information...
    dkms is already the newest version.
    dkms set to manually installed.
    linux-headers-3.2.0-4-amd64 is already the newest version.
    linux-headers-3.2.0-4-amd64 set to manually installed.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
    mount: warning: /mnt seems to be mounted read-only.
    Installing Virtualbox Guest Additions 5.1.16 - guest version is 4.1.18
    Verifying archive integrity... All good.
    Uncompressing VirtualBox 5.1.16 Guest Additions for Linux...........
    VirtualBox Guest Additions installer
    You appear to have a version of the VirtualBox Guest Additions
    on your system which was installed from a different source or using a
    different type of installer.  If you installed it from a package from your
    Linux distribution or if it is a default part of the system then we strongly
    recommend that you cancel this installation and remove it properly before
    installing this version.  If this is simply an older or a damaged
    installation you may safely proceed.
    
    Do you wish to continue anyway? [yes or no]
    
    Cancelling installation.
    An error occurred during installation of VirtualBox Guest Additions 5.1.16. Some functionality may not work as intended.
    In most cases it is OK that the "Window System drivers" installation failed.
    
    
    ==> default: Checking for guest additions in VM...
        default: The guest additions on this VM do not match the installed version of
        default: VirtualBox! In most cases this is fine, but in rare cases it can
        default: prevent things such as shared folders from working properly. If you see
        default: shared folder errors, please make sure the guest additions within the
        default: virtual machine match the version of VirtualBox you have installed on
        default: your host and reload your VM.
        default:
        default: Guest Additions Version: 4.1.18
        default: VirtualBox Version: 5.1
    ==> default: Setting hostname...
    ==> default: Configuring and enabling network interfaces...
    ==> default: Mounting shared folders...
        default: /vagrant => C:/Users/agarrido/Projects/mage2_vagrant
    Vagrant was unable to mount VirtualBox shared folders. This is usually
    because the filesystem "vboxsf" is not available. This filesystem is
    made available via the VirtualBox Guest Additions and kernel module.
    Please verify that these guest additions are properly installed in the
    guest. This is not a bug in Vagrant and is usually caused by a faulty
    Vagrant box. For context, the command attempted was:
    
    mount -t vboxsf -o dmode=777,fmode=777,uid=1000,gid=1000 vagrant /vagrant
    
    The error output from the command was:
    
    : No such file or directory`
    opened by adriagarrido 0
Owner
beeplogic
beeplogic
Vagrant Box for Magento 2 Developers

Vagrant project for Magento 2 developers (optimized for Mac, Windows and *nix hosts) ⚠️ Current project is not supported anymore. Please check out htt

Alex Paliarush 452 Oct 18, 2022
MageVagrant - Vagrant/Chef base box for running Magento

MageVagrant MageVagrant is a complete LAMP development environment for Magento. Specially created for the Magento Developer's Guide book. Features Aut

null 59 Sep 28, 2021
Provides a foundation for developing with Magento Commerce in a Vagrant box

Provides a foundation for developing with Magento Commerce in a Vagrant box. The machine is based on CentOS 6.4. ==== List of installed software. Mage

Jason Evans 19 May 12, 2017
Hi Im L, I found a box that I believe it's contain Kira's real ID. for open that box we need to find three keys. let's start looking for them

DeathNote ctf Description are you smart enaugh to help me capturing the three keys for open the box that contain the real ID of kira? Let's start solv

Hamza Elansari 4 Nov 28, 2022
Magento-Vagrant-Puppet-Nginx - Installs magento and a nginx server

Magento-Vagrant-Puppet-Nginx Installs Magento MySQL PHP PHP-FPM Nginx n98-magerun Setup git submodule init git submodule update vagrant up Modify pupp

Christian Münch 61 Aug 10, 2022
Automatically load the next page of products in Magento. Easy to install and configure, this module works 100% out of the box with vanilla Magento 1.9.x and earlier.

Automatically load the next page of products in Magento. Easy to install and configure, this module works 100% out of the box with vanilla Magento 1.9.x and earlier.

Strategery 123 Nov 20, 2021
This a php environment for developers. based on Vagrant & CentOS & laravel/homestead

Centstead 这是一个 PHP 调试环境 , 基于 centos,laravel/homestead. 介绍   基于开发的实际需求,PHP开发者通常需要一个贴近生产环境,又易于维护的测试与开发环境.以往的选择: xampp, wamp, phpstudy… 集成环境,启动方便,占用小,但是需

JasonChang 52 Sep 30, 2022
A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2

Simple Import / Export tool A tool that allows to quickly export data from Magento 1 and Magento 2 store and import it back into Magento 2. Table data

EcomDev B.V. 51 Dec 5, 2022
Dashboard that shows who pings your linux box - PHP and TCPDUMP

server-ping-alert Dashboard that shows who pings your linux box - PHP and TCPDUMP This uses tcpdump and php to see who is pinging your linux box. This

null 4 May 16, 2022
O manager Box é um projeto da disciplina de Projeto e prática 2 do IFPE - Igarassu, que consiste em uma aplicação web com funções de gerenciamento de estoque para pequenos empreendimentos.

ManagerBox O Manager Box é um projeto da disciplina de Projeto e prática 2 do IFPE - Igarassu, que consiste em uma aplicação web com funções de gerenc

Alan José 4 Apr 15, 2022
Box of Tricks for common PrePress related tasks.

PrePress Tricks Library Box of Tricks for common PrePress related tasks. Table of Contents Purpose Installation Basic Usage Purpose If you have ever a

null 1 Jul 26, 2022
Configure Magento 2 to send email using Google App, Gmail, Amazon Simple Email Service (SES), Microsoft Office365 and many other SMTP (Simple Mail Transfer Protocol) servers

Magento 2 SMTP Extension - Gmail, G Suite, Amazon SES, Office 365, Mailgun, SendGrid, Mandrill and other SMTP servers. For Magento 2.0.x, 2.1.x, 2.2.x

MagePal :: Magento Extensions 303 Oct 7, 2022
This Magento 2 extension integrates EasyTranslate into Magento 2.

EasyTranslate Magento 2 Connector This Magento 2 extension integrates EasyTranslate into Magento 2. Mind that you need to have an account with EasyTra

Easytranslate ApS 0 Oct 7, 2022
Magento-Functions - A Resource of Magento Functions

Magento-Functions A Resource of Magento Functions Table of Contents Category Product User Cart Checkout General Account [Working w/ URL's] (#urls) Cat

Bryan Littlefield 28 Apr 19, 2021
Magento - Magento Community Editions

Magento Community Edition /// THIS REPOSITORY IS DEPREACTED /// 1.9.4.1 will be the last version update. Please switch over to OpenMage! Either to the

FireGento e. V. 107 Oct 17, 2022
Docker-magento - Docker image for Magento 1.6 to 1.9

Docker image for Magento 1.x This repo creates a Docker image for Magento 1.x. Please note The primary goal of this repo is to create Docker images fo

Fu Cheng 144 Nov 18, 2022
Magento-composer-installer - Composer installer for Magento modules

!!! support the maintainer of this project via Patreon: https://www.patreon.com/Flyingmana Magento Composer Installer The purpose of this project is t

null 213 Sep 24, 2022