In this page we describe how to deploy a module.
You can have a look to the developer workflow for a global introduction of all developer steps from coding, developing and deploying.
Create your ScaleDynamics account
You need a scaledynamics account to deploy. You can sign up here to create your account. Subscription is FREE, no credit card required.
Install the SDK and start a session
If you haven't installed the SDK globally, you need to add it as a dependency to your module:
npm install warp
Before using the SDK you need to enter a session. You have to use your ScaleDynamics credentials to be identified using:
npx warp login
Select project and environment to deploy
The deployment of a server module requires to indicate in which project and which environment you want to deploy.
A project is a name that identifies a web site, a web app, a microservice or an API.
An environment is a name that identifies a cloud execution configuration to run modules. For example you can have 'pre-prod', 'demo', 'staging' or 'production' environments. Each one will have it's own cloud resource configuration.
Select a project
A project identifies a web site, a web app, a microservice or an API.
If you need to create a new project use
npx warp project create yourProjectName
To select a project use
npx warp project select yourProjectName
Select an environment
If you need to create a new environment use
npx warp env create yourEnvName
To select an environment to use
npx warp env select yourEnvName
Setup services for the environment
Before deploying you need to enable the Managed Node.js module service and assign cloud resources to it. To do that, open the console, select the organization, the server-test project and the demo environment. Then enable the Managed Node.js module service and assign a Shared Free cloud resource on the provider and the region you choose.
After subscribing resources, you will see in the console your services configurations.
Deploy the module in a cloud environment
To deploy use the
deploy command when you are located at the root of directory of your module you want to deploy. By default all assets in the directory are going to be deployed privately.
npx warp deploy
On the console you'll see what is going to be deployed and where.
See all options details in the
warp deploycommand line documentation.