Cella-CLI

Realtime global deployments.

With Cella's help, you can deploy and publish any kind of web application (or service) in under five minutes.

Usage

Firstly, make sure to install the package globally:

npm install -g cella-cli

Run this command in your terminal:

cella

For more examples, usage instructions and other commands run:

cella help

Introduction

The cella CLI is the main interface to the Cella platform.

It's available on macOS, Windows, and Linux either via npm. The recommended installation mechanism.

While the default behavior of cella is to deploy, it also has a variety of sub commands grouped by different concerns.

Cloud Commands

The following are the most important commands in Cella CLI:

| Syntax | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | cella [path] | When you invoke cella, the files within the current directory will be uploaded to Cella platform and a new deployment will be created. After that, you'll instantly receive its URL so that you can share it with other people around the globe. The [path] can either be a file (leads to a static deployment) or a directory (the deployment type will be determined depending on the contents). | | cella ls [app] | Show a list of all deployments. If [app] is defined, it will only list the deployments under that namespace. | | cella rm [id] | Remove a deployment from our platform. The [id] parameter can either be the URL of your deployment (e.g. https://static-ytbbrhoggd.cel-la.store or the hostname (e.g. static-ytbbrhoggd.cel-la.store). | | cella secrets [name] | Environment Variables and Secrets, show more pass cella secrets -h |

Deploying Node.js Apps

If your project contains a package.json (and no Dockerfile) file, it will always be treated as a Node.js deployment.

Note: You must defind start script within your package.json scripts part.