Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make webapp setup not require ssh #352

Open
c-w opened this issue Nov 17, 2017 · 4 comments
Open

Make webapp setup not require ssh #352

c-w opened this issue Nov 17, 2017 · 4 comments

Comments

@c-w
Copy link
Member

c-w commented Nov 17, 2017

What's this?

Currently to set up a new Lokole device, the user needs to:

  1. Burn an operating system to an SD card
  2. Mount the SD card in the Lokole device
  3. Connect the device to a router via Ethernet
  4. SSH into the device
  5. Download and run the setup script

This is a fairly technical process so it takes a bit of knowledge to setup a new device. It would be great if we could remove the SSH step from this process, e.g. by creating a custom OS build for Lokole.

Imported from https://github.com/ascoderu/opwen-setup/issues/4

@c-w
Copy link
Member Author

c-w commented Sep 5, 2018

Possible useful tool: https://github.com/treehouses (base RaspberryPi image with remote control for setup)

@sbathgate
Copy link
Member

I just came across this issue, is it still outstanding? Have you explored pi-gen? I have only taken a summary review, but it looks like it would do exactly what you are looking for. I am happy to explore the route and see if I can put together a solution.

The following is a link to the official GitHub repo: [https://github.com/RPi-Distro/pi-gen].
This website has a good walkthrough of the setup procedure: [http://kmdouglass.github.io/posts/create-a-custom-raspbian-image-with-pi-gen-part-1/]

@c-w
Copy link
Member Author

c-w commented May 15, 2019

To my understanding pi-gen is a tool to create a custom distribution, i.e., a Linux image that may already have some software we need pre-installed (e.g. supervisord, nginx, python3, etc.). This is very useful but only part of the story since we also need some dynamic content like the client registration. How do you recommend to handle this if we move to a pi-gen image?

@c-w
Copy link
Member Author

c-w commented May 15, 2019

Just brainstorming: one option could be to re-use the mechanism that Raspberry Pi uses to enable some optional features via optional text files (e.g. if /boot/ssh exists SSH is enabled)... after we burn the image, we place a file with the client name on a well known location and then on first boot a script can pick up that file and register the client.

I don't know much in this area so any help would be appreciated!

@c-w c-w transferred this issue from another repository Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants