Skip to main content

Version 5.0.0 - Excalibur

Below the list of updates in this release. Please have a look to Breaking changes with previous version of the plaform and Action required to know if you have something to do.

Updates and new features on the CLI

Introducting Runner management

See the Runner page for details.

On the CLI you can now get the list of runner models you can use to create a runner

  • Add command runner model list -

Get the list of created runners, create dynamically a runner, delete a runner and get info of the runner

  • Add commands runner list, runner create, runner delete & runner info

Move a container to another runner dynamically

  • Add command env runner set

deploy command extensions and limitations removal

  • You can now assign each container to the runner you select. A runner can run several containers.
  • You can deploy multiple containers during one deploy
  • Remove limit of deployment duration
  • Remove limit on total size of a deployment
  • Remove limit on individual file size
  • Add support of UTF-8 file name
  • Add support for long path and long file name
  • Add support for file and directory permission
  • Add support for symbolic and hard link

Build logs extension

Docker image build logs are now accessible

  • Extend command deployment logs with build level

Better interactivity

To speedup the selection of interactive fields

  • Add filter during prompt (match entries that contains the filter)

Updates and new features on the console

'Runners' view

Introduction of a new view that shows all Runners of an organization/project and which containers are running on them.

Metrics

Metrics are now provided for each Runner and for each container to give info to the developer.

Speedup project and env page loading time

Loading time has been improved for projet and env page.

Breaking change

  • Change default container name for docker and hosting. Before, the default name of the container was the name of the type of deployment (aka docker or hosting). Now this is the name of the parent directory. See Deployment.
  • The base url and runner configuration was linked on the type of the container (aka docker, hosting, server and module), now they are linked to the name of containers. See Deployment and Custom domains

Action required

If you have deployed containers with a previous version of the platform and want to redeploy

Although containers deployed with a previous version of the platform are still active, it is necessary to make a simple modification on your side of your deployment scripts in order to be able to redeploy these containers with the new version of the platform.

If you don't have a warp.config.js configuration file in the directory to deploy, you need to create a new one as follows:

  • If you are deploying a container of type 'docker' (dockerfile)
module.exports = {
docker: 'docker'
};
  • If you are deploying a 'hosting' type container (static assets)
module.exports = {
hosting: 'hosting'
};
  • If you are deploying a 'server' type container (nodejs server)
module.exports = {
server: 'server'
};
  • If you are deploying a container of type 'module' (nodejs module)
module.exports = {
module: 'module'
};

If you already have a warp.config.js configuration file in the directory to deploy, you need to modify it as follows.

If you specified the deployment type (docker: "xxx" or hosting: "xxx" or server: "xxx" or module: "xxx"), modify the line using the type as an attribute (docker: "docker" or hosting: "hosting" or server: "server" or module: "module"). If you did not specify the service type, add it as follows:

  • If you are deploying a container of type 'docker' (dockerfile)
module.exports = {
docker: 'docker'
};
  • If you are deploying a 'hosting' type container (static assets)
module.exports = {
hosting: 'hosting'
};
  • If you are deploying a 'server' type container (nodejs server)
module.exports = {
server: 'server'
};
  • If you are deploying a container of type 'module' (nodejs module)
module.exports = {
module: 'module'
};

If you allocated runners with a previous version

In case you have allocated runners with a previous version of the plateform, you will see them in the 'Runners' page of the console.

Nevertheless, these runners can only be used in the environment where you assigned them, so you cannot deploy another container on it if it is not part of the same environment.

If you want to have one runner running multiple containers of your organization, or project, you have to create a new runner, move the containers running on older runners to it, and delete the odler runner.