Merge branch 'master' of web-redpill@coreander:public_websites/source.redpill.dk/support_content

3 files changed, 104 insertions, 0 deletions

diff --git a/redpill/admin.mdwn b/redpill/admin.mdwn
new file mode 100644
index 0000000..b7c3985
--- /dev/null
+++ b/redpill/admin.mdwn
@@ -0,0 +1,52 @@
+# Redpill for technicians
+
+## Recommended hardware and software
+
+### Servere
+
+Hardware:
+
+ * Noname x86 machines
+ * software RAID
+ * All user data mirrored to remote host
+
+Software:
+
+ * Debian GNU/Linux (distribution)
+ * Postfix
+ * Apache
+ * AMaVis
+ * Dovecot
+ * HORDE/IMP
+
+### Workstations
+
+For creative use:
+
+ * Apple Macintosh
+
+For classical administrative use:
+
+ * Debian GNU/Linux or Microsoft Windows
+
+For use in schools or Internet cafés, at fairs or other demanding places:
+
+ * Debian GNU/Linux
+
+## Redpill in an alien environment
+
+It is possible to run a Redpill system at a host organisation not using (and
+with no interest in) the Redpill concept. The system usually need _not_ submit
+to a strict foreign policy.
+
+You need from the ICT staff of your host organisation...:
+
+ * A single static public IP number with port 22 open inbound and standard
+   ports open outbound (or ideally fully open)
+ * Space for a single standard-sized computer (or preferrably 2)
+
+
+## More info
+
+ * Strategic [[arguments|purpose]]
+ * Daily [[use]]
diff --git a/redpill/purpose.mdwn b/redpill/purpose.mdwn
new file mode 100644
index 0000000..e0e8928
--- /dev/null
+++ b/redpill/purpose.mdwn
@@ -0,0 +1,27 @@
+# Redpill for decision makers
+
+Redpill is the opposite of outsourcing: As much as possible of your precious
+data and infrastructure in kept in-house, and the rest uses only simple and
+generic services to avoid depending on unique features of a single provider.
+
+An "ICT guide" is hired part-time to help setup your resources as
+self-sustainable as possible, and to train one or more of your own staff to
+work with the system on a day-to-day basis.
+
+When the setup is completed, smaller tasks like restarting services or
+adding/changing user accounts can be done by the "superusers" among your staff.
+Beyond that, your network can in principle run on its own. In reality you are
+recommended to keep your ICT guide in the loop as a technical advisor,
+continuously checking security and optimize/improve/extend services.
+
+You keep your ICT guide only for as long as the relationship is mutually
+beneficial: Your data, services and know-how stays with you. Your system keeps
+running, it just slowly becomes "oldfashioned". And you can take in other ICT
+guides or ordinary technicians - all code is Free Software, tied to the Debian
+GNU/Linux distribution with one of the largest userbases worldwide and favoured
+especially amongst skilled networks administrators.
+
+## More info
+
+ * Daily [[use]]
+ * Technical [[overview|admin]]
diff --git a/redpill/use.mdwn b/redpill/use.mdwn
new file mode 100644
index 0000000..d96fcfc
--- /dev/null
+++ b/redpill/use.mdwn
@@ -0,0 +1,25 @@
+# Redpill for users
+
+At a Redpill system you are the hero! You are offered various tools to use as
+you please, at your own pace.
+
+If problems occur along the way, then no god or magician wipes it off for you,
+but you are not all alone either...
+
+At some other systems, technical stuff is considered too important to involve
+you - or you are too important to get involved. Technicians are your servants
+and superheroes, taking care of technical challenges on your behalf.
+
+With Redpill, however, [[communicating|internet]] is considered too important
+to leave to others. Computers are servants (but sometimes clumsy at that),
+while technicians are skilled friends helping you if in trouble - not by
+carrying you, but by guiding and enlightening. And maybe use a little magic
+now and then too, but too much would spoil you.
+
+Redpill makes you the hero!
+
+## More info
+
+ * Strategic [[arguments|purpose]]
+ * Technical [[overview|admin]]
+ * [[../Intro]] to this Redpill-based system