platformio / platformio/platformio-core

Remote Development without PIO account

Open
#3,689 10 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature remote
Dominant language
Python
Stars
9.5k
Forks
905
Avg merge
2d 13h
Merged PRs (30d)
2

Description

Description of problem

At my university we would like to use PIO for some courses. For some tasks we provide the students with remote development boards which they can currently access over a virtual machine with a programmer and webcam attached. However such vms are relatively slow and have a high latency as the IDE and tooling also run on the vm.

The remote development capabilities would be a perfect replacement for this however we cannot require our students to create PIO accounts. Therefore it would be very nice if one was instead able to just provide the IP of the machine running the remote agent instead of needing an account setup on both machines. Optionally it would be nice to be able to protect the remote agent with a password however for our use case this is all set up using firewall rules.

Another alternative solution I stumbled upon in the forum would be to enable people to set up their own broker (i.e. the PIO Cloud in the technology overview) which is where the agents advertise themselves to and what the clients query to get remote devices. This would also be beneficial for larger setups where the IP is unknown but the local network is disconnected from the internet.

Additional info

Related discussions in the forum: Pio remote without login? and In-house remote server

Pinging @ivankravets as he apparently knows best how this works and said that they would look into this.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start with the linked remote-development technology overview and the two related forum discussions to understand the current account and broker flow. Done would require a settled, specified approach for accountless IP-based access or an in-house broker, including its security model.

Written by the indexing model from the issue text.

Assessment

Domain
devtools, embedded-iot, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.