Note: This document is updated due to 4.0 Jelastic version.

With the help of Jelastic Packaging Standard we’ve packaged the most popular and requested applications, previously configured in the most beneficial way. These applications can be automatically installed directly from the dashboard, skipping many steps of manual deployment, or from our Marketplace site page by means of one-click installation widgets.

Beside that, the Jelastic Marketplace dashboard section offers you an easy way to operate with environment add-ons and Docker containers within the appropriate dedicated sections. The first section provides the ability to update your running environments with some custom configurations, while the second one allows to add the desired application or service Docker templates directly to your new (or existing) Docker-based environments in several clicks.

To access the Jelastic Marketplace via dashboard, just click the corresponding button at the top pane.

You’ll see a new tab opened, with the following sections inside:


Upon expanding the Apps Marketplace section (with an arrow button near its name), you’ll be shown a full list of available applications, divided into the appropriate categories, at the left. This allows you to choose among the available solutions depending on your needs.

Follow the instruction below in order to install any of the available packaged applications.

1. To find a particular application, use a special Search box above the apps list. Simply type application’s name (or part of it) into this field and choose the required one from the drop-down list. We’ll use the Wordpress CMS as an example.

2. Then hover over the found app and click the Install button at the unfolded frame in order to automatically create the appropriate environment and deploy the chosen application to it.

3. In the opened Confirm installation of application window, type the preferable name (or leave the default one) and select a region (if available) for the environment you would like to create and deploy the chosen application to.

Click Install to continue.

4. The process of installation will be started. Wait a minute for Preparing, Deploying and Configuring to be finished.

5. After these operations are completed, you'll see a frame with the corresponding administration data listed (which is also duplicated within the appropriate email notification).

Click the Open in browser button.

6. Your ready-to-work application will be opened in a new browser tab.

That’s all! Now you can enjoy using your application.


The second board within the Marketplace section contains a number of add-ons, that could be installed over the existing environments to apply the required modifications to the comprised nodes, their settings, topology, etc.

So, in order to patch your environment, you need to perform the following:

1. Switch to the corresponding Add-ons pane, where you’ll see the list of available packages and a Search field right above them for the quick and easy access to the desired element.

For example, let’s look for the TimeZone change add-on.

2. Hover over the found package to see its description and click the appeared Install button to initiate the corresponding action.

3. Within the appeared confirmation frame, select the target environment (i.e. that should be adjusted) and specify the rest of configuration parameters, required for the add-on’s appliance. In our case, it is a new time zone for the application - for example, let’s choose the America/Chicago one.

4. After that the installation will be started, which may take a couple of minutes (the exact duration depends on a type of operation that is performed by an add-on).

5. Wait for the installation process’ success message to be appeared (the corresponding email notifications will be sent as well).

Now, you can check the appropriate nodes’ settings and ensure the new configurations were applied to your environment.


The Containers section is devoted to operating with Docker images and contains the following tabs:

  • Quick Start with a set of most popular templates (this tab is optional, so its presence depends on your hosting provider’s settings)
  • Search, which allows to find the desired template at the central Hub Registry
  • Custom, where you can add your own template from your custom registry

Installing the desired software can be done just in a few clicks - find the required image, choose it to be deployed, select the necessary tag from the list of automatically fetched ones and specify the preferable name of your new Docker®-based environment (or apply the template addition to the existing one).

Tip: The complete guide on Docker containers’ management through the Jelastic Marketplace can be found here.

The list of Docker® templates, which are shown at the Quick Start tab, can be enlarged via your JCA panel through following the next steps:

1. Navigate to its Marketplace section and click on the New installation option inside the Add menu.

2. Then, in the opened code editor, select the Docker option from the Template drop-down list at the top pane.

Edit the strings inside with information, required for the desired Docker® image addition. The following main parameters should be specified:
  • application > name - appellation, that will be displayed for this template at the Docker® Containers board
  • categories - there are two possible values here, which define the image's availability within the Quick Start tab: the dockers/apps string sets it to be displayed at the Containers board in Marketplace, and the dockers/stacks value means it will be shown in the Select Container frame of the Docker tab inside the environment wizard.
    Note:  You can additionally define a Docker template to be displayed only for a particular environment layer by extending declared parameter with the corresponding [/layer] suffix, i.e. balancing, app-servers, cache, sqldb, nosqldb and others respectively
  • env - in this section you can state the Jelastic SSL option to be obligatory enabled (by substituting the corresponding false value with true) in a newly created Docker®-based environment with the current image. All the rest of values should not be modified.
  • dockerImage  >
    • name - identifier of the required Docker® image in the repository/image format
    • registry - optional parameter for the case this image is located at your custom repository (i.e. not at the central Hub Registry). Thus, if it’s needed, specify your registry’s hostname here
    • username and password - optional parameters for image’s access credentials in case it’s private
  • settings > fields > dockertags > values - here you can state which tags will be available for a user while deploying this Docker® image. The default value is latest, nevertheless, it can be deleted for the whole list of image tags being automatically fetched, so any of them could be chosen before the deployment.

The extended specification on all the available parameters and settings will be provided in the nearest future.

Click on the Save button below the editor when finished.

3. In order to test the deployment process for the added Docker® template before providing it to the end-users, add the following parameter at the end of your dashboard URL:


Herewith, the example link should be substituted with the http:// or https:// URL to the JSON manifest file of your package (the one you’ve edited in the previous step), uploaded wherever in the Internet. This will initiate the process of template installation.

Pay attention, that such an URL should not contain the question mark "?", otherwise it won't work properly. In this case you'll need to use some URL shortener.

4. Finally, choose the added template within the list of Marketplace packages and select Publish in the panel above in order to make it available for your users.

After that, the selected Docker® image will be listed at the Quick Start tab of the Docker® Containers board alongside the default ones.
to be displayed only for a particular environment layer by extending the dockers/stacks parameter with the corresponding [/layer] suffix, i.e.: balancing, app-severs, cache, sqldb, nosqldb and others.