# 1. Deploy plgd Cloud
There are multiple options how to start using / testing the plgd Cloud. If you're just trying to get in touch with this Cloud Native IoT framework, jump right to the [try.plgd.cloud](#Try plgd.cloud) instance and onboard your device right away. In case you want to get in touch with the system localy and you have the Docker installed (opens new window), use our plgd cloud #Bundle.
Helm chart for the k8s deployment is in progress. Contributions welcome! (opens new window)
The plgd team operates their own instance of the plgd cloud for free. This cloud instance is integrated with the plgd mobile application available for both iOS and Android based devices. Together with our IoTivity-Lite sample you're able to onboard and work with your device remotely in couple of seconds. To start right away, follow try.plgd.cloud (opens new window). More information about the mobile application is available in the Onboard Getting Started section.
Bundle deployment hosts core plgd Cloud Services with mocked OAuth Server in a single Docker image. All services which hosts the gRPC or HTTP API are proxied through the NGINX with configurable
FQDN. Mobile application documented in the Onboard Getting Started section works also with the Bundle.
Bundle version of plgd services should be used only for simple testing and development purposes. Performance evaluations, production environment or other sensitive deployments should deploy plgd services using the plgd HELM chart.
# Run on localhost
To deploy and access plgd cloud on your local PC using bundle, run single command:
docker run -d --name plgd -p 443:443 -p 5683:5683 -p 5684:5684 plgd/bundle:v2next
After couple of seconds your plgd cloud will become available. The plgd dashboard can be opened in your browser at https://localhost/ (opens new window).
Note that bundle issues it's own self-signed certificate which needs to be accepted in the browser.
The plgd cloud doesn't work without OAuth Server. To not require developers not interested in sharing bundle instance with other users, simple mocked OAuth Server is included in the bundle. Authentication to the plgd is therefore not required and test user is automatically logged in. Same applies also to device connections; in case you're using the bundle, devices connecting to the CoAP Gateway can use random/static onboarding code as it's not verified. Onboarding of devices is therefore much simpler.
Authorization Service which is part of the plgd is only for testing and development purposes. For the production, integration of the plgd device identity management API is required.
Even for the development and testing, more complex scenarios are supported by the built-in authorization service. Read more in the Developing with plgd.
- By default the plgd cloud bundle hosts the NGINX proxy on port
443. This port might be already occupied by other process, e.g. Skype. Default port can be changed by environment variable
-e NGINX_PORT=8443. Please be aware that the port needs to be exposed from the container ->
-p 443:443needs to be changed to match a new port, e.g.
- Logs and data are by default stored at
/datapath. Run the container with
-v $PWD/vol/plgd/data:/datato be able to analyze the logs in case of an issue.
- In case you need support, we are happy to support you on Gitter (opens new window)
- OCF UCI (Cloud2Cloud Gateway) is not part of the bundle