Skip to content
This repository has been archived by the owner on Aug 6, 2018. It is now read-only.

Deployment considerations #25

Open
sumnerevans opened this issue May 11, 2018 · 4 comments
Open

Deployment considerations #25

sumnerevans opened this issue May 11, 2018 · 4 comments
Labels
tracking Tracks the progress of some large change/set of changes

Comments

@sumnerevans
Copy link
Member

sumnerevans commented May 11, 2018

I want to make a list of deployment considerations. We do not need to address these for a while (we have to stabilize everything else out first), but I want to have this here so that we can keep track of what we've been thinking.

  1. How will be bundle libvisplaygui?
  2. AUR Package (because, duh).
  3. We should consider creating a custom image that can be loaded straight onto a Raspberry Pi.

Feel free to add more considerations to this list.

@sumnerevans sumnerevans added the tracking Tracks the progress of some large change/set of changes label May 11, 2018
@robozman
Copy link
Member

My concern for the custom image is that it's a lot to deploy, for example an entire raspbian image that is up to date. Maybe just an install tutorial (NO PIPING WGET TO SH) for base raspbian.

@sumnerevans
Copy link
Member Author

NO PIPING WGET TO SH

😂 Agreed.

My concern for the custom image is that it's a lot to deploy

Also agree. This would be a very long term goal, if we make it a goal at all. Honestly, it's probably best to make Visplay so robust that anyone can run it on any Linux box. Getting a Visplay package in the AUR is probably a good goal in the more foreseeable future though.

@robozman
Copy link
Member

Snap / Flatpack could also maybe be a long term goal. Not sure what RPi support for these distribution methods is

@sumnerevans
Copy link
Member Author

Snap/Flatpak is a good idea for the server, especially.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tracking Tracks the progress of some large change/set of changes
Projects
None yet
Development

No branches or pull requests

2 participants