You are browsing documentation for version 5.1 of OroCommerce, supported until March 2026. Read the documentation for version 6.0 (the latest LTS version) to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

Vagrant Provision 

To get familiar with the application functionality, you can install Oro applications with environment components using Vagrant.

Every Oro application has a Vagrantfile that enables you to set up a virtual machine with the Oro application via the vagrant up command.

For example, to set up a VM with OroCommerce CE application v. 5.1.0 locally, run:

git clone -b 5.1.0 oroapp && cd oroapp
vagrant up

Once the command has run, you can access the application via the URL.

The environment in the resulting VM and the provisioning steps in the Vagrantfile replicate the process described in the Setup Application Environment Guide and the Installation Guide.

For more details on preparing the virtual platform for the virtual machine, please see the Installation and Configuration section below.

Installation and Configuration 


  • Windows, macOS, Linux, or any other OS supported by Virtualbox and Vagrant

  • 4096M available RAM on your PC

Installation Steps 

Start by installing the required software:

  1. Install VirtualBox.

  2. Install Vagrant.

  3. Install Git.

When you have installed VirtualBox, Vagrant, and Git, do the following:

  1. Get the Oro application source code:

    git clone -b 5.1.0 <oro_application_clone_url> oroapp && cd oroapp

    Replace the <oro_application_clone_url> with the repository URL for the necessary Oro application:

    OroCommerce Community Edition

    OroCommerce Community Edition for Germany

    OroCommerce Enterprise Edition

    OroCommerce Enterprise Edition for Germany

    OroCommerce Enterprise Edition (without CRM)

    OroCRM Community Edition

    OroCRM Enterprise Edition

    OroPlatform Community Edition

    OroCommerce Platform


    You can download and unpack the archive with the Oro application source code instead of using the Git repository. For more information, please see Get the Oro Application Source Code.

  2. Configure and run the virtual machine using Vagrant:

    For Community Editions of the Oro Applications run:

    vagrant up

    for the Enterprise Editions of Oro applications, specify the following two environment variables:

    • gittoken - Github token use it to install Oro application dependencies

    • licence - Enterprise Licence key for your Oro Application

    for Linux bash example:

    gittoken=YourGithubToken licence=YourEnterpsiseLicenceKey vagrant up

    for Windows PowerShell terminal example:

    $env:licence = "YourEnterpsiseLicenceKey"; $env:gittoken = "YourGithubToken"; vagrant up


    At the first start, vagrant will ask you to install the required vagrant-env plugin. You must agree (press Y) and repeat the command vagrant up.

    Once the command execution is complete and the setup is finished, you can use the Oro application.


    When you run vagrant up for the first time, the Oro application installation may take some time, as the following time-consuming provisioning steps happen:

    • InstallBaseSystem - Base Oracle Linux 8 box download. Upgrade and install docker and docker compose plugin

    • Build - Run composer install for the Oro application in docker. Create docker image

    • Install - Oro application installation; note that loading demo data takes extra time.

    • Deploy - Deploy application

    The total time for the environment to get up and running depends on multiple factors, such as internet connection speed, CPU frequency, etc. It usually takes from 1- to 15 minutes.


    You can re-run all or one of the required steps. For example, if the application code has changed, then you need to restart 3 steps: - Build, Install, Deploy.

    vagrant provision --provision-with Build,Install,Deploy

Customize Installation Process 

To customize the default installation settings, add the required variables in .env-build.

Application settings

ORO_SAMPLE_DATA=n                # y | n (whether to perform loading demo data during installation)

To customize the application hostname:

  • Set the new ORO_APP_DOMAIN parameter value in the .env-build (e.g., yourdomain.local)

  • Map the new hostname to the application host IP address in your local hosts file, like in the following examples: yourdomain.local www.yourdomain.local

Now you can open the Oro application in a browser via the http://yourdomain.local/ URL.

Running Multiple Virtual Machines 

To run multiple virtual machines simultaneously on a single host, ensure that every virtual instance uses a unique forwarded port. Before running an additional instance, modify its forwarded port in the host section of the “forwarded_port” setting in the Vagrant file. You can increment the value for every new virtual instance, e.g., instance A can have “forwarded_port”, guest: 80, host: 8000 configuration, and instance B can have “forwarded_port”, guest: 80, host: 8001. Also you should change port in variable ORO_WEBSOCKET_FRONTEND_DSN=//*:8000/ws for websocket frontend.

Access the Installed Oro Application 

Once the VM setup has finished, you can access the application in your browser with the credentials defined by your installation configuration.

The default login details are:

  • Application Storefront URL:

  • Application Admin UI URL:

  • Admin Login: admin

  • Admin Password: admin

If you have changed the application host, admin login, or password, please refer to the .env-build for these details.

Shared Working Directory 

Vagrant maps the working directory on your host machine to the /vagrant directory in the virtual machine file system. Once the VM is up, any changes to the files in the host working directory are applied to the /vagrant directory in the virtual machine file system, and vice versa. To update the application, you need to run the provision steps Build, Install, Deploy again.

vagrant provision --provision-with Build,Install,Deploy

SSH Access to the Virtual Machine 

To connect to the virtual machine via SSH, run the following command in the working directory on your host machine:

vagrant ssh

You will be logged in to the virtual machine as vagrant user with sudo permission (you do not need a password to use the sudo command).

To configure SSH access to the virtual machine for the utilities that run on the host machine, like IDE, get the explicit SSH credentials by running the following command:

vagrant ssh-config

Vagrant Сommands 

  • vagrant up – Creates and configures the virtual machine according to the Vagrantfile. Unless vagrant destroy has been launched on consecutive runs, vagrant up powers on the virtual machine. The provisioning scripts run only once.

  • vagrant provision –provision-with Build,Install,Deploy – Run provisioning scripts defined in the Vagrantfile.

  • vagrant halt – Stops the virtual machine and saves the virtual machine image (without the current RAM state) to the host hard drive.

  • vagrant suspend – Stops the virtual machine and saves the virtual machine image and the current RAM state on the host hard drive.

  • vagrant resume – Resume the suspended virtual machine.

  • vagrant destroy – Destroys the virtual machine and frees the host machine’s resources.

For more information, please see the official Vagrant documentation.