Barputer-Next

From Voidwarranties - Hackerspace Antwerp, Belgium
Revision as of 10:38, 2 August 2014 by Yvanj (Talk | contribs)
Jump to: navigation, search


Barputer-Next
What:
Rebuilding the barputer, with a touch of cloudlyness.
Cloud.jpg
Participants:
Bramsky, warddr
Category:
Art
Locations:
Den Bunker, 10.98.254.144

Contents

Outline

Concept

Since the barputer lives in a pretty harsh environment, a backup strategy is required. The last one left us at a moment whe didn't expect it to fail, and accounting is an issue for those who pay their drinks monthly. My idea was to put the barputer and related software in a VM (without Apache <= 2.2.19, or even without Apache at all), and access it remotely. I recently starded exploring x2go. X2go is somewhat like a RDP alternative for linux, a free/OSS version of NXServer.

It is currently possible to run a full desktop, or a minimized environment which allows you to run the Cash Register application only.

The advantages of x2go/NX are:

The disadvantages are:

Important stuff

Shutdown routine:

Powerup routine:


What has been done?


What should still be done?

Notes

Sidenotes

Why cloudlyness?

Apparently everybody calls "something not on this computer" nowadays "something somewhere in the cloud". It's just goin' with the flow, so everybody understands eachother.

Why remote?

Should be clear by now; moving the Single Point Of Failure to a location which doesn't has the fail rate of the location of the current barputer. We're using the space to cook now (below the barputer), and since we started doing it, the barputer has failed. Moisture from the cooking process doens't have anything to do with it, right? Due to the moisture issues in the space, everything of great importance should be kept out of it.


Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Content Creation
Belgian Spaces