That's it! Your application is running in the
Deploy the Application
To deploy an application to Arrow Cloud
If the application is already deployed, you need to either increment the
To deploy an application stored in a Github repository to Arrow Cloud
To generate a Github personal access token:
The token will be available in the Applications page of your settings.
View Log Files
An application typically runs in the cloud, so being able to see what is happening in the application is very important. Any log output written to
The Appcelerator CLI provides three commands for viewing logs for a published application, accesslog, logcat, loglist.
About logged execution times
The execution time reported by the
And below is the corresponding
The application can import any third-party modules that are supported by standard Node.js applications. Before publishing the app to the cloud, make sure all dependencies are listed in the
The Arrow Cloud
Once you have added these modules as dependencies, use
Define Environment Variables
To set environment variables, use the
You can access the environment variables from the application using the
To unset an environment variable, use the
To check the current environment variables, use the
You cannot use the following names for environment variables: "appid", "basedir", "bodyParser", "customConfig", "dirname", "framework", "fullpath", "name", "serverId", "port", "version", "NODE", "NODE_PATH", "PATH", "PWD", "PORT", "TMPDIR", and "USER".
After changing an environment variable, you will be prompted to restart the application.
The following example sets the
Scale the Application
To customize the number of cloud servers the application can enable the auto-scaling feature to automatically scale up and down the number of cloud servers based on the number of queued requests. You specify the maximum number of queued requests that should occur before the application is scaled up. You can also specify the minimum and maximum number of servers that should be used.
The following example enables autoscaling, using a maximum of five servers, when there are at least 20 queued requests. The application is also configured to automatically scale down the number of servers when the number of queued requests drops below 20.
Set a Custom Domain and Path
You can bind a custom domain to your application that points to either a CNAME record or A record as well as assign it a path.
The alias to set should be a valid domain name that has been already configured with either a CNAME or A record pointing to the published application's URL. Appcelerator Cloud validates the domain record before binding it to the application.
To bind a domain to an application, use the
If you need to remove a domain, use the
To route an application based on a path with the domain name, use the
The following example allows the application to be accessed from
For example, if your published URL is
Each application can use 1.8 GB of diskspace. The application can only write files to the project's root directory and to the
Each application runs in a specific container size with different resources (memory and number of CPUs). By default, when the application is published, it will run in one Dev container.
You can specify one of the following container sizes depending on your Appcelerator Platform subscription:
If your application gets archived, to reactivate the application, make a request to it. The first request will be slow, but subsequent requests will respond with normal speed.
Note that each container your application runs on costs a certain number of points. To see how many points you have used and are allocated, or to see which containers your application is using, execute the
Currently, Arrow Cloud