diff options
author | elijah <elijah@riseup.net> | 2015-06-19 00:36:27 -0700 |
---|---|---|
committer | elijah <elijah@riseup.net> | 2015-06-19 00:36:27 -0700 |
commit | 702b9e594b616637326760623c8b9d2e9ea4e0de (patch) | |
tree | 76b3523b29dc91e8f8031b811aa8e545b555736b /pages/services/technology/platform | |
parent | 32cc0dd47c5998804fc4f0c77f603b2800e3310d (diff) |
added platform/services documentation, removed /services (/services text is better on bitmask.net anyway).
Diffstat (limited to 'pages/services/technology/platform')
-rw-r--r-- | pages/services/technology/platform/en.haml | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/pages/services/technology/platform/en.haml b/pages/services/technology/platform/en.haml deleted file mode 100644 index 44bbce9..0000000 --- a/pages/services/technology/platform/en.haml +++ /dev/null @@ -1,16 +0,0 @@ -%h1.first git clone leap-platform - -%p The LEAP Provider Platform is the server-side part of LEAP that is run by service providers. It consists of a set of complementary packages and recipes to automate the maintenance of LEAP services in a hardened GNU/Linux environment. Our goal is to make it painless for service providers and ISPs to deploy a secure communications platform. - -%p The LEAP Platform is essentially a git repository of puppet recipes, with a few scripts to help with bootstrapping and deployment. A service provider who wants to deploy LEAP services will clone or fork this repository, edit the main configuration file to specify which services should run on which hosts, and run scripts to deploy this configuration. - -%h1 More providers, please - -%p We believe that the best way to defend the right to whisper is to bring encryption technology into wider adoption. Despite growing awareness of the importance of communication security, users who attempt to adopt better practices still have few places they can turn. - -%p Most people think of lack of security as a problem of insufficient demand. We think that there are actually enough people out there who would like to use communication tools with higher security but who face severe problems of supply. - -%p The goal of LEAP is to meet this demand with tools that are usable and secure. But the LEAP architecture is necessarily a #{link 'federated' => 'infosec'} one, and the enhanced security it provides is only possible once there is a health ecosystem of service providers using the LEAP platform. - -%p One way to get more service providers is to make the people who run them happy. With the LEAP Platform, we want to reduce the amount of bullshit work. We are not "dumbing down" the work it takes to run a service provider. Rather, our goal is to allow talented sysadmins to focus on the parts that really matter and spend less time wrestling with the frustrating and mundane aspects of system administration. - |