Skip to main content

2. Download and install the CLI

2a. CLI and local running of Wasm Apps​

We call hosts (machines) running outside of Cosmonic but connected to the same flat mesh network "Stargate hosts". These are the core of extending Cosmonic to any cloud or edge, and can be easily started from our CLI.

To set up a Stargate host on your local machine, you can install our CLI:

bash -c "$(curl -fsSL https://cosmonic.sh/install.sh)"

And then run up to start a Stargate host on your local machine:

cosmo up

2b. Running the same application split between the cloud and your machine​

Next we are going to see how easy it is to run the same components of an application split between hosts. One of the powerful things about Cosmonic is that your basic application architecture can be deployed to dramatically different application topologies, all without changing or modifying your architecture.

To do this, we need a second remote host. We label our remote hosts "Stargate".

Deploying a new version of the application​

Deploying a new version of an application is as simple as updating the manifest. We have already done that for you, which you can launch from the button below

OS-specific

Note this new manifest is OS-specific, and setup for macOS currently. If you are using a different OS, you can update the hostcore.os to either windows or linux

Deploy on Cosmonic & Stargate

In the new manifest, we updated the version and specified new requirements for our XKCD Actor and the HTTP client. New wadm

And that's it! It's the same application, running in the same secure network, now communicating between two sets of totally different infrastructure with different underlying system architectures! You can still access it through the same ingress wormhole (DNS address), and it works the same way 🎉

What's next?​

Next, let's turn to local development and see how easy it is to make a change with Cosmonic and have that run on any machine, still as part of the same application. Head on to Make It Your Own to learn more!