Spin up a demo Magento Open Source instance, in the cloud, in one click.
Or, with Adobe Commerce and/or Hyvä Themes in 3 simple steps.
This repository contains a Gitpod configuration for a Magento 2 cloud environment that can be used for multiple purposes, such as:
- To demo sites to merchants during sales pitches
- To provide merchant training sessions
- Quick access to a blank Magento instance to test/debug default configuration options
- For a demo instance to help revise for Adobe Commerce certifications (e.g. Business Practitioner)
- For a quick, disposable development environment to 'hack around' on (great for developer training sessions)
- For those new to Magento 2 to quickly get hands-on and play around with the platform
- Environments are quick to create (~5 mins) and even faster to restart, once created, after being stopped (<1 min)
- Each environment allows you full access to the storefront, admin panel, codebase, command line and more, and can even be connected to VS Code or PHP Storm remotely
- Everything is cloud hosted, so it takes up no space or resource on your machine (bar another browser tab)
- Each environment has it's own dedicated URL, which you can share others so they can access too (e.g. merchants and colleagues)
- You can create, run (and destroy) as many environments as you like and run up to 4 in parallel (on the free tier)
- Gitpod's free tier provides you 50 hours of uptime across all environments
- After 30 minutes of inactivity your instance will be turned off to save your usage time
Be aware that after 14 days of inactivity your environment will be deleted!
- Ensure you have a GitHub account and are logged in
- Install and enable the (Gitpod browser extension)
- Ensure you have the relevant license keys to hand (for Adobe Commerce and Hyvä Themes only)
- Navigate to the default
open-source
branch here (or stay on the main repo page) and click the 'Gitpod' button, or simply visit https://gitpod.io/#https://github.com/fisheyehq/magento-gitpod
- Create a free Gitpod account by linking your GitHub account: https://gitpod.io/login/
- Add variables to your account at https://gitpod.io/variables for
MAGENTO_COMPOSER_AUTH_USER
andMAGENTO_COMPOSER_AUTH_PASS
with composer credentials that have access to the Adobe Commerce repos and set the scope tofisheyehq/magento-gitpod
* - Navigate to the
adobe-commerce-b2b
branch here and click the 'Gitpod' button, or simply visit https://gitpod.io/#https://github.com/fisheyehq/magento-gitpod/tree/adobe-commerce-b2b
*Note: you must supply your own composer credentials to allow install of Adobe Commerce. The default credentials in this repo support Magento Open Source only.
- Create a free Gitpod account by linking your GitHub account: https://gitpod.io/login/
- Add variables to your account at https://gitpod.io/variables for
HYVA_COMPOSER_TOKEN
andHYVA_COMPOSER_PROJECT
with your Hyvä Themes composer token and project name (see Hyvä's install docs for more detail) and set the scope tofisheyehq/magento-gitpod
* - Navigate to the
hyva-themes
branch here and click the 'Gitpod' button, or simply visit https://gitpod.io/#https://github.com/fisheyehq/magento-gitpod/tree/hyva-themes
*Note: you must supply your own Hyvä credentials that where provided to you when purchased a license. Installing Hyvä Themes via git is not supported.
- Ensure you've followed steps 1 and 2. from both the Adobe Commerce and Hyvä Themes guides above
- Visit: https://gitpod.io/#INSTALL_HYVA=YES/https://github.com/fisheyehq/magento-gitpod/tree/adobe-commerce-b2b
The Magento Admin Panel is is available at /admin
and the username and password are admin
and password1
respectively.
The environments allow for multiple different configuration settings that can be overridden using environment variables, including (but not limited to):
- Installation of Magento Open Source or Adobe Commerce
- Installation of sample data
- Magento version to install
- Installation and set up of Hyvä Themes
- Composer credentials
- PHP/MySQL/Nginx/Redis etc, versions
- Enabling Xdebug
- Change the admin username and password
To see a full list of environment variables that can be overridden see all lines that begin with
ENV
in the .gitpod.Dockerfile file.
There are multiple ways to override environment variables, which are outlined in this guide, and which option you should choose depends on whether you want to override the configuration for a specific environment only, or every environment you create with Gitpod.
To override values for all environments, which is recommended if you want to override composer credentials to allow installation of Adobe Commerce, see the Adobe Commerce set up steps above (under 'Getting Started') to add variables to your account at https://gitpod.io/variables. You may also wish to use this to always enable Xdebug, for example.
There are some settings that you may want to override for a specific environment only, such as whether you want to install sample data, or change the version of Magento installed. You can do this by passing the environment variables as part of the URL to initiate the environment build.
All the 'Gitpod' button on GitHub does is direct you to a special Gitpod URL that includes the GitHub repo URL. For example, on this repo the URL is https://gitpod.io/#https://github.com/fisheyehq/magento-gitpod
.
To override variables, they need to included between https://gitpod.io/#
portion of the URL and the repo URL itself.
For example to install Magento 2.4.4 (managed by the MAGENTO_VERSION
variable) and disable the installation of sample data (managed by the INSTALL_SAMPLE_DATA
variable) you'd construct and visit the following URL:
Note: for security reasons, it is not recommended to pass sensitive information (such as composer credentials) as URL parameters. Always use the https://gitpod.io/variables page in your account instead.
- Magento Open Source support
- Adobe Commerce support (and allow overriding of composer credentials)
- Add Magento sample data
- Install and enable B2B for the Adobe Commerce build
- Add Hyvä Themes support
- Add Adobe Live Search and Product Recommendations to the Adobe Commerce build
- Add useful, often used solutions for demo purposes, e.g. Elasticsuite, ShipperHQ, Braintree etc.
- Add Mage-OS as a repository option for Magento Open Source
- Add option to install Magento Open Source from GitHub for core code contributions
Further roadmap suggestions and pull requests welcome.
Based on the original Gitpod development environment and config produced by