Environment Options

There are various environment options available when engaging with Elastic Path. Each option is designed to fit a purpose or audience and as a result the completeness of each environment is adjusted accordingly. Options are ordered in the table as a progression from left to right with completeness building as you progress in this direction. Generally, as you move through the enablement process you will progress through these environment options in this order, likely with some overlap.

Elastic Path Demo Accessibility

Elastic Path Demo packages are only available to Elastic Path Partners. If you are not an Elastic Path Partner, please contact your Elastic Path Sales Representative to discuss.

This section contains guides related to infrastructure and practices used in the construction phase of an Elastic Path project.

note

These guides reference technologies and practices commonly used on internal Elastic Path projects. These technologies and practices are designed to work together.

Your organization may decide to use different technologies and practices. If you do so, be aware that deviating from the documented technologies, configuration settings, and implementation steps (except where stated) might result in your team or developer environments not working properly.

Local Elastic Path Demos

The purpose of this option is to:

• Review or demonstrate front-end functionality
• Review or demonstrate back-end administration or operations

This environment consists of Elastic Path Demo package and is easy to setup and install. However, this demo does not include the source code.

Accessing Elastic Path Demos

1. Download the demo files from the support portal and unzip
2. Follow the setup instructions.

Training environment

This environment is used for:

• Training
• Code evaluation
• Proof of concept

Environment elements:

• AWS (Amazon Web Service) Windows VM

Accessing Training Environment

1. Sign in to the Learning Center.
2. Search for Create a Self-Managed Commerce VM (Training Environment) in the content library.
3. Follow the access instructions that will be sent to you through email.

This environment is a complete individual developer environment that contains Commerce Engine, Cortex, Studio, and the Reference Store. You can make code changes and rebuild.

important

You have a limited number of days to access this environment and only one user can access it at a time.

Individual Dev Environment

This environment is used for:

• Advanced learning
• Code evaluation
• Proof of concept

Environment elements:

• Maven repository
• Local developer setup

For using this environment, follow the Starting Construction guide setup instructions for:

• Maven Repository Specifications
• Setting Up Local Developer and Quality Assurance Environments

This environment is a complete local developer environment. However, this environment does not support team development.

Development Team Environment

This environment is used for:

• Construction or project implementation
• Proof of concept

Environment elements:

• Source control
• Maven repository
• Continuous integration
• Dev team server
• Local developer setup

For using this environment, follow the Starting Construction guide setup instructions for the complete team environment.

This environment is a complete complete team environment and is ready for project extensions.