Setting up Platforms one by one
For setting up remote.it on Raspberry Pis one by one, you can use one of:
- the remoteit.Pi SD card image
- Raspbian or other OS with the remoteit package installed
- Raspbian or other Pi OS with the connectd package installed
Using remote.it in mass production
To easily configure many devices with the same set of remote.it Services, you should use one of two similar mass production approaches offered in the connectd package for Linux.
- Auto Registration
- Bulk Registration
If you are using a Windows or Mac platform as a remote.it endpoint and wish to mass produce the configuration, please contact firstname.lastname@example.org.
We use a few common terms that have very specific meanings in the following pages.
Platform: Any type of mass produced embedded system used with remote.it, such as a cell modem or a Raspberry Pi. The Platform is a physical object.
Application: A program such as ssh, nginx or tightvncserver that communicates with a client program using a single TCP socket. A remote.it Service enables the user to remotely connect to an Application.
Service: A remote.it connection to an Application. For example remote.it allows the user to connect via a Service to an Application such as an ssh Application or a vnc Application. For example the vnc Application may be RealVNC or tightvncserver. Each remote.it connection is viewed by remote.it as a separate Service. Every remote.it Service should be attached to an Application. Services are implemented using the connectd daemon.
Product: A template defining a set of Services you wish to install on a Platform.
Device: A set of remote.it Services installed on a Platform using the Product template and registered to a remote.it account.
Click on this button to start by creating a Product Definition, or keep scrolling down to learn more about Auto and Bulk Registration.