Barputer-Next

From VoidWarranties - Hackerspace Antwerp, Belgium
(Difference between revisions)
Jump to: navigation, search
Line 40: Line 40:
 
=Notes=
 
=Notes=
 
* username/password is the same as the old one. (ask in the space, posting them on the wiki is not a good idea)
 
* username/password is the same as the old one. (ask in the space, posting them on the wiki is not a good idea)
* it's a Debian, sudo won't work like it does in Ubuntu. Use <code>su -</code> for now to become root, return to normal privileges with ctrl+d/logout, untill I fix it.
+
* it's a Debian, sudo won't work like it does in Ubuntu. Use <code>su -</code> for now to become root, return to normal privileges with ctrl+d/<code>logout</code>, untill I fix it.
 
* IP is 10.98.254.144, should be accessible by VPN and inside the network.
 
* IP is 10.98.254.144, should be accessible by VPN and inside the network.
 
* X2go settings: Gnome, FullScreen, ADSL Speed (or whatever suits the connection),... Leave most things in the default state, except KDE->GNOME and Desktop 800x600->FullScreen.
 
* X2go settings: Gnome, FullScreen, ADSL Speed (or whatever suits the connection),... Leave most things in the default state, except KDE->GNOME and Desktop 800x600->FullScreen.
 +
 +
=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.

Revision as of 11:13, 8 February 2012


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


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.

The advantages of x2go/NX are:

The disadvantages are:

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