Jelastic 5.6.4

This document is preliminary and subject to change.

In this document, you will find all of the new features, enhancements and visible changes included to the Jelastic PaaS 5.6.4 release.

Additional Domains for Environments

API methods to assign additional domains for a whole environment, its node groups or particular containers

Learn more
Sign In with Tokens

An ability to access the dashboard using the appropriate token instead of the account password

Learn more
Marketplace Amendments

Categories reorganization and the Docker Containers section removal

Learn more
Software Stack Versions

Actualized list of supported OS templates and software stack versions

Learn more
Bug Fixes

List of fixes applied to the platform starting from the current release

Learn more

Additional Domains for Environments

Jelastic PaaS provides multiple default domain names for environments, node groups, and separate containers. Starting with the current 5.6.4 platform release, a possibility to assign additional domain names was implemented. Three new BinderService API methods were developed to support a new functionality:
  • AddDomains(envName, session, domains, [nodeGroup], [nodeId]) - assigns additional domains to the specified envName environment. Using the optional nodeGroup or nodeId (has a higher priority if both are specified) parameters, you can set domains for the particular layer or node


    • Multiple domains can be provided as a comma- or semicolon-separated list.
    • Domains are provided in a short form, i.e. ${envName} for the environment (${envName}.${platformDomain}) or ${subDomain} for the layer/container (${subDomain}.${envName}.${platformDomain}).
    • The provided environment domains (${envName}) should be no less than five characters and are validated across the existing DNS records; the maximum length for subdomains (${subDomain}) is 32 characters.
    • If adding domains for the whole environment (not for the particular layer or node), they are assigned to the appropriate entry-point (i.e. load balancer or application server layer)
  • RemoveDomains(envName, session, domains, [group], [nodeId) - detaches the listed domains from the whole environment or its particular layer/node (provide * to remove all of the additional domains). Herewith, the default domains are skipped, so only custom ones can be removed
  • GetDomains(envName, session, [nodeGroup], [nodeId], [inShort, default=true]) - lists all the domains assigned to the envName environment. The response can be narrowed by the optional nodeGroup or nodeId (has a higher priority if both are specified) parameters. Set the inShort parameter as false to view domains in the extended form

Also, the response of the GetEnvs and GetEnvInfo API methods was extended with the new aliases section, where the assigned domains are listed in a short form.

More info

Back to the top

Sign In with Tokens

Within the Jelastic 5.6.4 release, a possibility to share access to the dashboard via personal access tokens was implemented. Herewith, such operation requires Extended Access, which can be selected from the API drop-down list within the Generate Access Token form.

extended access personal token
Note: The dashboard access cannot be provided via a custom token with a full API Access, as it requires an API Access + Web UI Access (which can be obtained via the Extended Access API set only).

After successful logging in with a token, all the functionality of the account owner will be available, excluding the possibilities to change the account password, manage two-factor authentication and adjust access tokens.

More info

Back to the top

Marketplace Amendments

In the present 5.6.4 platform upgrade a major revision of the Jelastic Marketplace was done. The existing categorization system was thoroughly reviewed and updated, removing the unpopular groups and including the trading topics. Within these categories, the packages were reorganized by positioning the most frequently used solutions at the beginning, which ensures simpler and quicker access to them.

jelastic marketplace

Another notable change is the removal of the Docker Containers section from the Marketplace tab, where its presence becomes excessive. This functionality is fully covered in the topology wizard frame, where it can be managed with greater convenience and additional possibilities (for example, to build complex environments with multiple custom Docker containers).

More info

Back to the top

Software Stack Versions

Check out the list of the most accurate Jelastic software stacks for the current platform version:

StackJelastic 5.6.4
Apache Balancer2.4.37
Apache PHP2.4.37
Apache Python2.4.37
Apache Ruby2.4.37
CentOS (VPS)6.8; 7.2
Couchbase CE5.1.1; 6.0.0
Docker Engine CE17.12; 18.09
GlassFish3.1.2.2; 4.1.2; 5.1.0
MariaDB5.5.62; 10.3.12
MongoDB2.6.12; 3.6.8; 4.0.2
MySQL CE5.7.25; 8.0.14
NGINX Balancer1.14.2
NGINX Ruby1.14.2
NodeJS6.16.0; 8.15.0; 9.11.2; 10.15.0; 11.7.0
Payara4.1.2.181; 5.184
PostgreSQL9.6.11; 10.6; 11.1
Redis4.0.11; 5.0.3
Spring Boot2
Tomcat7.0.92; 8.5.37; 9.0.14
Ubuntu (VPS)16.04
Varnish4.1.8; 5.2.1; 6.1.1
WildFly10.1.0; 11.0.0; 12.0.0; 13.0.0; 14.0.1; 15.0.1
Windows (VPS)2012
JDK6.0_45; 7.0_79; 8.0_202; 9.0.4; 10.0.2; 11.0.2
Open JDK7.0_201; 8.0_191; 10.0.2; 11.0.2; 12.ea-b30; 13.ea-b6
OpenJ90.9.0-8u181-b13; 0.9.0-; 0.9.0-10.0.2; 0.11.0-8u192-b12; 0.11.0-11.0.1
PHP 55.3.29; 5.4.45; 5.5.38; 5.6.40
PHP 77.0.33; 7.1.26; 7.2.14; 7.3.1
Ruby2.2.10; 2.3.8; 2.4.5; 2.5.3; 2.6.0
Python 22.7.15
Python 33.4.9; 3.5.6; 3.6.7; 3.7.1
Node.js6.16.0; 8.15.0; 9.11.2; 10.15.0; 11.7.0

Back to the top

Bug Fixes

This information will be provided in the nearest furure.

Back to the top