This guide will help you set up Space Cloud via Docker.
The following command runs
space-cloud in a docker container and exposes the HTTP and gRPC endpoints on ports
docker run -d -p 4122:4122 -p 4124:4124 --name space-cloud \ -e ADMIN_USER=some-admin \ -e ADMIN_PASS=some-pass \ -e ADMIN_SECRET=some-secret \ spaceuptech/space-cloud:latest
ADMIN_PASS are the credentials to login into Mission Control (Admin UI), whereas
ADMIN_SECRET is the JWT secret used to authenticate requests made via. Mission Control.
Note: The HTTP and grpc endpoints are available in a secure fashion over SSL on ports
To expose the HTTP and grpc endpoints of Space Cloud in a secure way via SSL run the following command:
docker run -d -p 4126:4126 -p 4128:4128 --name space-cloud \ -v /path/to/ssl-certs:/ssl -e ADMIN_USER=some-admin \ -e ADMIN_PASS=some-pass \ -e ADMIN_SECRET=some-secret \ -e SSL_CERT=/ssl/some-ssl.crt \ -e SSL_KEY=/ssl/some-ssl.key \ spaceuptech/space-cloud:latest
Check if the
space-cloud container is up and running:
If you exec into docker container of Space Cloud, you can see a
config.yaml file and a
raft-store folder would have been generated in the home directory.
Space Cloud needs this config file in order to function. The config file is used to load information like the database to be used, its connection string, security rules, etc.
Space Cloud has it’s own Mission Control (admin UI) to configure all of this in an easy way.
Note: All changes to the config of
space-cloudhas to be done through the Mission Control only. Changes made manually to the config file will get overwritten.
Open Mission Control
Head over to
https://YOUR_URL:4126/mission-control to open Mission Control depending on how you started
YOUR_URLwith the address of your Space Cloud if you are not running it locally.
Awesome! We just started Space Cloud using Docker. Next step would be to set up a project to use Space Cloud in your preffered language.
Feel free to check out various capabalities of