Once you have done the first deployment manually or you have already in the platform the packages for the 2 components of the application (the server and the client), you can simply deploy a manifest file that describe the topology of the application with a single command: apc manifest deploy cast-microservice.json

apc-manifest-deploy-cast-microservice.json

Deploying manifest...
[manifest] -- Deploy -- execution started
[manifest] -- Deploy -- looking up "package::/sandbox/simone::cast-client"
[manifest] -- Deploy -- looking up "package::/sandbox/simone::cast-server"
[manifest] -- Deploy -- checking if policy allows binding "job::/sandbox/simone::castclient" to "service::/sandbox/simone::nats-server"
[manifest] -- Deploy -- checking if policy allows binding "job::/sandbox/simone::castserver" to "service::/sandbox/simone::nats-server"
[manifest] -- Deploy -- skip creating "service::/sandbox/simone::nats-server" since it already exists
[manifest] -- Deploy -- creating "job::/sandbox/simone::castclient"
[manifest] -- Deploy -- created "job::/sandbox/simone::castclient"
[manifest] -- Deploy -- creating "job::/sandbox/simone::castserver"
[manifest] -- Deploy -- created "job::/sandbox/simone::castserver"
[manifest] -- Deploy -- binding "job::/sandbox/simone::castclient" to "service::/sandbox/simone::nats-server"
[manifest] -- Deploy -- binding "job::/sandbox/simone::castserver" to "service::/sandbox/simone::nats-server"
[manifest] -- Finish -- execution was successful
╭──────────────────────────────────┬─────────┬───────────┬────────┬────────╮
│ Job FQN                          │ Status  │ Instances │ Subnet │ Errors │
├──────────────────────────────────┼─────────┼───────────┼────────┼────────┤
│ job::/sandbox/simone::castclient │ started │ 1         │ N/A    │        │
│ job::/sandbox/simone::castserver │ started │ 1         │ N/A    │        │
╰──────────────────────────────────┴─────────┴───────────┴────────┴────────╯
Success!