- Project structure
- Initializer file
- Deploy the application
- Log output
- View log files
- Node version
- Port binding
- Install custom binaries
- Declare dependencies
- Define environment variables
- Scale the application
- Access a specific container
- Custom domains
- Add a custom SSL certificate
- Create child processes
- Application limitations
An API Builder application is a standard Node.js application that runs in the API Runtime Services environment. This guide covers how to manage your project.
A project is made up of several components. To simplify development, API Builder primarily uses a strict directory structure and naming convention to organize the application rather than configuration files.
The following is a list of directories and files that can be found in a project:
|Entry point to the application if it is used as a server. You can monitor the startup and shutdown sequence.|
|Contains component dependencies and API Runtime Services deployment settings. For details, see API Runtime Configuration.|
|Contains configuration files in JSON format for the project and required connectors. For details, see Console Configuration.|
Contains generated docs for your project's APIs.
|Contains Endpoint JSON files, these are OpenAPI 2.0 (Swagger) documents used to create custom entry points for the application, with execution logic defined by linked Flows|
|Contains Flow JSON files, used for defining business logic for Endpoints.|
|Entry point to the application if it is used as a module.|
|Contains generated log files when running your project locally.|
|Contains project dependencies. API Builder automatically installs any project dependencies declared in the |
|nodes||Contains custom nodes for use in Flows. Nodes must be node.js packages in their own folders named |
|NPM configuration file to declare project dependencies and other build or runtime configurations. For details, see NodeJS Configuration.|
|Contains installed service connectors used within Flows for connecting to and interacting with external services.|
|Contains Web files, used to create endpoints that render UI.|
|Contains template files for your Web interface. Files must have one of the following extensions: |
app.js file contains code that initializes the server instance. You can hook into the lifecycle events of the server as well as make additional setup or middleware calls to the server or Express app instance.
For example, the following
server.app.use call forces the client to use a secure connection by redirecting any unsecured connections to the HTTPS URL.
Deploy the application
To deploy an application to API Runtime Services, run the
appc publish command from the API Runtime Services project directory. Your project source code will be uploaded to the API Runtime Services where
npm install will be executed against the project, which downloads and installs any NPM module dependencies. When installation completes, the application is executed using
If the application is already deployed, you need to either increment the
version field in the
package.json file to publish a new version of the application or pass the
--force flag to the publish command to republish the application. Before republishing the application, API Runtime Services sends the
SIGTERM signal to the currently deployed application to let it shutdown gracefully. If the app does not shutdown in time, API Runtime Services will kill the application.
API Runtime Services can capture two kinds of log output from applications:
- access logs – HTTP requests to the application
- application logs – explicit log calls made in the application
To capture access logs, use the
console.error() methods, or you can use the
By default, when an application is initialized, it loads and creates an
appc-logger instance. The
appc-logger instance is bound to the server instance, which will automatically capture access logs for the application.
To make log calls, use the
logger property from either the API Builder instance, request object or response object to invoke
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
stderr in the application's root process is captured and stored by API Runtime Services, and can be viewed using the Appcelerator command-line tool or in the Logs tab of the Dashboard.
- Only output written by the application's root process is included in the log file; output written by child processes forked by the application's root process will not be caught.
- Errors such as syntax errors, application crashes, and system level failures are logged automatically.
The Appcelerator CLI provides three commands for viewing logs for a published application, accesslog, logcat, loglist.
appc cloud accesslogcommand lists all requests processed by the Appcelerator Cloud in a specified time period. By default, a maximum of 100 log messages is returned at a time.
appc cloud loglistcommand lists your published application's log for a specific period. By default, a maximum of 100 log messages is returned at a time.
appc cloud logcatcommand lists your published application's log continuously from Appcelerator Cloud.
About logged execution times
The execution time reported by the
accesslog commands report slightly different values. The
accesslog command reports the time required by Appcelerator Cloud to handle the initial user request, pass it to your Node application for processing, and deliver the response. In contrast,
loglist only reports the execution time for your application itself, not including the time required to process the request and response. Consequently, the
accesslog execution times are a slightly longer than those of the corresponding
loglist log item. For instance, below is
And below is the corresponding
Prior to API Runtime Services (formerly known as Arrow Cloud) 1.2.0, the only Node versions you could use were 0.8.26 and 0.10.22.
Starting with API Runtime Services 1.2.0, you may specify any version of Node. Node 0.8.26, 0.10.22 and 0.12.4 are built in, but other versions will be downloaded from https://nodejs.org/ when the application is built prior to running
npm install. The Node version is managed by the 'n' module (https://github.com/tj/n).
To specify a Node version, in the
package.json file, set the
engines.node key to the version of Node you want to use. DO NOT SPECIFY A RANGE. If you do not specify a Node version, the application will use 4.4.7 by default (as of SDK 6.0.0).
Starting with API Runtime Services 1.2.0, you may explicitly set the port the application listens on. Set the
cloud.environment.PORT key in
appc.json file. or use the
appc cloud config --set "PORT=<PORT_NUMBER>" command to set the special environment variable PORT. If you do not set PORT explicitly before publishing your application, API Runtime Services sets it to 80 by default.
Verify that the application listens on PORT, otherwise your app cannot be connected. Use
process.env.PORT in the application to verify the application is connected to a port.
Install custom binaries
API Runtime Services allows you to install additional binaries before your application is built.
Starting with API Runtime Services 1.3.0, to install additional third-party tools, create a script called
install.sh in the project's root folder, which installs the required packages.
Below is a sample script located at
./install.sh folder in the application's directory.
Prior to Release 1.3.0, you needed to create a script in your project folder (no name restrictions) and add the script to the
package.json file. In the
package.json file, set the
scripts.postinstall field to the path to the script:
Note that from API Runtime Services 1.3.0 and later, you can still use the above method but do not name the script
install.sh or it will run twice, and only install the binaries in the project directory. Prior to API Runtime Services 1.3.0, binaries could be installed outside the project directory.
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
dependencies field in the application's
package.json file. For example, to add support for MongoDB 1.2.0 or greater:
Define environment variables
To set environment variables, add them to the
cloud.environment object in the project's
You can also use the Appcelerator CLI to manage the environment variables.
To set environment variables, use the
appc cloud config --set <key>=<value> command. To set more than one variable at a time, comma separate the key-value pairs.
You can access the environment variables from the application using the
process.env namespace. For example, if you set a variable called
process.env.foo to access it in the application.
To unset an environment variable, use the
appc cloud config --unset <key> command.
To check the current environment variables, use the
appc cloud config --env command.
After changing an environment variable, you will be prompted to restart the application.
The following example sets the
foo environment variables, lists all set environment variables, then unsets 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. API Runtime Services will increase the number of containers if the queue is too high for at least one minute. You can also specify the minimum and the 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.
You can also use the
appc cloud config command to configure autoscaling:
Access a specific container
Starting with API Runtime Services 1.3.1, if you have scaled your application to use more than one server container, you can make a request to a specific container that your application is running on. To make a request to a specific server container, pass the
_serverid parameter with the request and set it to the ID of the server container. To retrieve the server container ID, run the
accesslog --show_serverid command.
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. When setting the domain, do no specify the protocol, that is, do not prefix the URL with
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 set a custom domain, set the
cloud.domain field in the
appc.json. You can optionally set the
cloud.domainPath field to assign a path to the application. The following example sets a domain and path on the application that can be accessed from
You can also use the Appcelerator CLI to manage the domain and path.
To bind a domain to an application, use the
appc cloud config --set <domain_name> command to bind a domain to the application. You can bind multiple domains to an application. Use the
--set <domain_name> parameter to bind up to five additional domains to the application.
If you need to remove a domain, use the
--remove parameter. For applications with multiple domains, you will be prompted to select which domain to remove. You may optionally pass the domain name to remove with the
To route, an application based on a path with the domain name, use the
appc cloud config --path <path_name> command to set a path for the application after setting a domain. For example, if you want to bind two applications to the same domain, specify a path for each to route a client to the correct application.
The following example allows the application to be accessed from
The following example allows the LegacyApp application to be accessed from
www.foo.com/v1 and the BrandNewApp application to be accessed from
cloudapp.appcelerator.com URL that Appcelerator Cloud uses to publish your application supports a wildcard subdomain. You may append a token to the beginning of the URL that can be parsed by the application. This does not apply to custom domain names using the
acs domain command to bind the application to a CNAME or A record.
For example, if your published URL is
https://1234567890.cloudapp.appcelerator.com/, you can navigate to your application using the same domain and add a custom token as the subdomain, for example,
deadbeef is the wildcard subdomain. Then, the application can retrieve the host and subdomain:
Add a custom SSL certificate
To use a custom SSL certificate to access your application using HTTPS, you need to create a PEM file, then add the PEM file to the application.
To create a PEM file, you will need the following three files provided by your SSL certificate provider:
- Certificate file (
customapp.com.crt, for example)
- Intermediate certificate authority (
gd_bundle.crt, for example)
- Key used to generate the certificate (
customapp.com.key, for example)
You need to combine the contents of the three files into a single text file, called a PEM file, which you will add to your application. The PEM file must have the following structure:
Use a text editor or the
cat command to merge the files together:
Once you have created the PEM file, set the
cloud.certificate field to the path of the certificate file.
You can also add it to your application by executing the following command:
Create child processes
A single instance of Node runs in a single thread. To take advantage of multi-core systems, you can launch a cluster of Node processes to handle the load. Applications can use the core Node Cluster module to easily create child processes that all share server ports.
To use this feature you application uses cluster.setupMaster() to set a path to a custom file to use for each child process. A cluster should listen on port 9000 or greater to avoid port conflicts. If the port your application is trying to listen on is in use, a
EADDRINUSE error will result. Your application must also have privileges to listen on the specified port, otherwise, an
EACCES error will result.
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 Medium container.
- To specify a bigger container for the application, set the
cloud.containerfield in the
appc.jsonfile or use the
appc cloud servercommand.
- To use more than one container for your application, see Scale the Application.
You can specify one of the following container sizes depending on your AMPLIFY Appcelerator Services subscription:
|Name||Point Cost||Memory||CPU Shares||Archive Behavior|
|Dev||1||512MB||1000||After an hour of inactivity|
|Small||2||256MB||1000||After a week of inactivity|
|Medium||4||512MB||2000||After a week of inactivity|
|Large||8||1024MB||4000||After a week of inactivity|
|XLarge||16||2048MB||8000||After a week of inactivity|
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
appc cloud list command.
Currently, API Runtime Services only supports applications opening one server listening port. There cannot be more than one TCP/HTTP server started in one application.