Overview
Goal
The goal is to set up the DTaaS infrastructure in order to enable your users to use the DTaaS. As an admin you will administrate the users and the servers of the system.
Optional Requirements
There are three optional requirements for installing the DTaaS. These requirements are not needed for localhost installation. They are only required for installation of the DTaaS on a web server.
OAuth Provider
The DTaaS software is uses OAuth for user authorization. It is
possible to use either
Domain name
The DTaaS software is a web application and is preferably hosted
on a server with a domain name like
Reverse Proxy
The installation setup recommends that the foo.com server is behind a reverse proxy / load balancer that provides https termination. You can still use the DTaaS software even if you do not have this reverse proxy.
Install
The DTaaS can be installed in different ways. Each version serves a different purpose. Follow the installation that fits your usecase.
| Installation Setup | Purpose |
|---|---|
| Trial installation on localhost | Install DTaaS on your computer for a single user; does not need a web server. This setup also does not require reverse proxy and domain name. |
| Production installation on single host | Install DTaaS on server for multiple users. |
| One vagrant machine | Install DTaaS on a virtual machine; can be used for single or multiple users. |
| Two vagrant machines | Install DTaaS on two virtual machines; can be used for single or multiple users. |
| The core DTaaS application is installed on the first virtual machine and all the services (RabbitMQ, MQTT, InfluxDB, Grafana and MongoDB) are installed on second virtual machine. | |
| Seperater Packages: client website and lib microservice | Can be used independently; do not need full installation of DTaaS. |