opeNode (https://www.openode.io/) command line to control and manage your application instances efficiently.
opeNode provides reliable and fast Platform As A Services (PaaS) to deploy your web applications instantly.
npm install -g openode
First, just go to your project directory in command line:
cd [your project directory]
And then just type:
This command will upload your local repository to the opeNode cloud, npm install, then launch a secure container of your server, and then put it online. During this command, you can also select between using a subdomain.openode.io or a custom domain.
Note that when you run openode deploy and your website is already running, it will update your files, update the environment variables (if they changed), and reload your website.
openode deploy [-t TOKEN -s SITE_NAME] [repository URL]
.openodeignore: If you add a .openodeignore file in your repository, the list of files provided in this file will get ignored (not sent). The format is the same as the well known .gitignore.
If you want to switch to a different user, just use:
If you would like to deploy without synchronizing the files, this is the right command to use:
openode restart [-l locationId] [--with-latest-deployment]
The --with-latest-deployment uses the latest deployed image instead of rebuilding a new one.
If you want to synchronize the files prior to deploy the following command can be used.
Note that this is a temporarily remote location, NOT the live files. When you run openode sync, files are basically prepared. Then when you hit openode deploy, these files are built into an image.
In order to upgrade your plan, you first have to look at the possible plans using:
Pick the right id, and then you can upgrade by running:
openode set-plan PLAN_ID
You can always verify which plan is currently active with:
To change the currently active instance, type:
openode change-instance [SITENAME]
To integrate with your favorite continuous integration (CI) tool, you can use the following command in order to generate the .openode file:
openode ci-conf TOKEN SITENAME
Note that you can avoid using ci-conf and provide the token and sitename by using the -t and -s options in the deploy command, for example: openode deploy -t yourtoken -s yoursitename.
You can obtain the info on your website instance via:
You can view the logs by using the following command:
openode logs [-n nbLines]
The following command allows to run a command in your running container:
openode exec [yourCmd]
For example, if you run openode
exec "ls -la", the list of files will be listed.
In order to clear the temp (see the sync command for more details) remote folder, run:
To enable a custom domain, make sure to enter your custom domain while running openode deploy. Then you can manage your custom domain subdomains using the following commands.
openode add-alias [hostname]
If your custom domain is for example mycustomdomain.com, then you can run
openode add-alias www.mycustomdomain.com openode add-alias blog.mycustomdomain.com
in order to point mycustomdomain.com, www.mycustomdomain.com, and blog.mycustomdomain.com to this instance.
openode del-alias [hostname]
To list all DNS settings
A new DNS entry can be added with:
openode add-dns [domainName] [type] [value] [priority]
where the domainName is the domain name, type is the DNS entry type (A, TXT, etc.), and finally a value must be set. A priority can be set for MX type records.
To delete a DNS entry:
openode del-dns [id]
where id corresponds to the id returned by list-dns.
openode create-snapshot <path>
Creates a snapshot of the content in given folder.
The following commands allow to manage locations where your website is deployed.
openode add-location [location-id]
openode del-location [location-id]
Templates are Dockerfile which can be copied to your local. The Dockerfile is what we use to deploy your instances. You are free to use as is a Dockerfile template or adapt it to your needs.
To view the list of all available templates, type:
To get the template description:
openode template-info [template-name]
To get a copy of a template, just do:
openode template [template-name]
Note that if you do not specify a template name, the CLI will get the most appropriate template based on your local repository.
Website configs, such as the build script path, can be managed via the CLI.
openode set-config [variable] [value]
openode config [variable]