girish@cloudron.io 28baef8929 Go back to using docker exec in cloudron exec
The main issue is that multiple cloudron exec sessions do not
share the same rootfs. Which makes it annoying to debug.

We also have some nginx timeout which drops you out of exec
now and then resulting in loss of all state.
2016-01-15 15:24:46 -08:00
2015-11-05 19:29:08 +01:00
2016-01-14 10:51:21 -08:00
2016-01-14 10:55:53 -08:00
2016-01-11 11:15:04 +01:00
2015-12-10 13:08:38 -08:00
2016-01-14 13:30:08 -08:00
2016-01-14 15:53:32 +01:00
2016-01-15 11:28:43 -08:00
2016-01-13 10:42:45 +01:00

Cloudron a Smart Server

Selfhost Instructions

The smart server currently relies on an AWS account with access to Route53 and S3 and is tested on DigitalOcean and EC2.

First create a virtual private server with Ubuntu 15.04 and run the following commands in an ssh session to initialize the base image:

TODO curl from a well known released version of installer.sh
./installer.sh <domain> <aws access key> <aws acccess secret> <backup bucket> <provider> <release sha1>
S
Description
Cloudron Box
Readme 47 MiB
Languages
JavaScript 72.6%
Vue 22.3%
Shell 3.1%
HTML 1.1%
EJS 0.7%
Other 0.2%