
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
alacrity-cli
Advanced tools
Command Line Interface for AlaCrity.
AlaCrity is a modern automated app deployment & web server manager.
Fore more information see AlaCrity.com
Always refer to the documentation bundled in CLI as it is the most updated one. You can view the help by alacrity --help or alacrity deploy --help or etc.
This guide assumes that you have started AlaCrity on a linux server and setup your DNS (see AlaCrity Setup).
You can use this CLI tool to perform initial AlaCrity server setup, and to deploy your apps.
Before anything, install the CLI tool using npm:
npm install -g alacrity
You can use the CLI by typing alacrity in your console.
The CLI has several commands, if invoked without a command it display the usage summary:
Usage: alacrity [options] [command]
CLI tool for AlaCrity. See AlaCrity.com for more details.
Options:
-V, --version output the version number
-h, --help output usage information
Commands:
serversetup|setup [options] Performs necessary actions to prepare AlaCrity on your server.
login [options] Login to a AlaCrity machine. You can be logged in to multiple machines simultaneously.
list|ls List all AlaCrity machines currently logged in.
logout [options] Logout from a AlaCrity machine and clear auth info.
deploy [options] Deploy your app to a specific AlaCrity machine. You'll be prompted for missing parameters.
api [options] Call a generic API on a specific AlaCrity machine. Use carefully only if you really know what you are doing!
Almost all commands require some data to work. Data for commands can be provided from different sources:
ENV_VAR=value alacrity command);-c, --configFile and ALACRITY_CONFIG_FILE), command options names define the keys of the configuration file;If the same data is provided from different sources, the priority order reflects the above list (the following ones overwrite the previous ones), except for input prompt that is used only if that data is not provided from others sources.
View help for a command to know more details to that command, by running:
alacrity [command] --help
The very first thing you need to do is to setup your AlaCrity server. You can either do this by visiting HTTP://IP_ADDRESS_OF_SERVER:3000 in your browser, or the recommended way which is the command line tool.
Simply run:
alacrity serversetup
Follow the steps as instructed: enter IP address of server and the root domain to be used with this AlaCrity instance. If you don't know what AlaCrity root domain is, please visit AlaCrity.com for documentation. This is a very crucial step.
After that, you'll be asked to change your AlaCrity server password, and to enter your email address. This should be a valid email address as it will be used in your SSL certificates.
After HTTPS is enabled, you'll be asked to enter a name for this AlaCrity machine, to store auth credential locally. And... Your are done! Go to Deploy section below to read more about app deployment.
For automation purposes, you can provide necessary data before to be prompted for them, for example using a config file like:
{
"alacrityIP": "123.123.123.123",
"alacrityPassword": "alacran42",
"alacrityRootDomain": "root.domain.com",
"newPassword": "rAnDoMpAsSwOrD",
"certificateEmail": "email@gmail.com",
"alacrityName": "my-machine-123-123-123-123"
}
And then running:
alacrity serversetup -c /path/to/config.json
Note: you can also use either YAML or JSON.
If you've done the "Server Setup" process through the command line, you can skip "Login" step because your auth credential are automatically stored in the last step of setup.
This command does login to your AlaCrity server and store your auth credential locally.
It is recommended that at this point you have already set up HTTPS. Login over insecure, plain HTTP is not recommended.
To login to your AlaCrity server, simply run the following command and answer the questions:
alacrity login
If operation finishes successfully, you will be prompted with a success message.
Note: you can be logged in to several AlaCrity servers at the same time; this is particularly useful if you have separate staging and production servers.
For automation purposes, you can provide necessary data before to be prompted for them, for example using a config file like:
{
"alacrityUrl": "alacran.root.domain.com",
"alacrityPassword": "alacran42",
"alacrityName": "testing-1"
}
And then running:
alacrity login -c /path/to/config.json
Note: you can also use either YAML or JSON.
Use this command to deploy your application. Deploy via alacrity CLI supports 4 deployments methods: alacran-definition file, Dockerfile, tar file, and image name (see Alacran Definition File for more info).
Simply run the following command and answers questions:
alacrity deploy
You will then see your application being uploaded, after that, your application getting built.
Note: based on your deployment method, the build process could take multiple minutes, please be patient!
For automation purposes, you can provide necessary data before to be prompted for them, for example directly on the command line by running:
alacrity deploy -n machine-name -a app-name -b branchName
Note: you must be logged in to "machine-name".
This can be useful if you want to integrate to CI/CD pipelines.
See command help to know more details and deployments methods.
Use this command to see a list of AlaCrity machines you are currently logged in to.
Run the following command:
alacrity list
Use this command to logout from a AlaCrity machine and clear auth info.
Run the following command and choose a AlaCrity machine:
alacrity logout
Use this command to call a generic API on a AlaCrity machine, specifying API path, method (GET or POST), and data. There is no official document for the API commands at this point as it is subject to change at any point. But you can use ApiManager.ts as a starting point.
alacrity api
For automation purposes, you can provide necessary data before to be prompted for them, for example using a config file like:
{
"alacrityName": "server-1",
"path": "/user/apps/appDefinitions/unusedImages",
"method": "GET",
"data": {
"mostRecentLimit": "3"
}
}
And then running (using environment variable for config file value):
ALACRITY_CONFIG_FILE='/path/to/config.json' alacrity api -o output.json
Note: use carefully only if you really know what you are doing!
FAQs
CLI tool for AlaCrity. See AlaCrity.com for more details.
We found that alacrity-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.