Girish Ramakrishnan
f8c683f451
Story so far: 1. App installed from store. appStoreId is set to manifest.id. 2. User installed a custom built app with a custom manifest.id using cloudron install --app <id>. The appStoreId is still set. 3. When we make a new release, it overrides the users install. The fix (for now) is: 1. Do not allow mismatching ids to start with. 2. When forced, it is allowed but appStoreId is cleared so as to not get any auto updates. This leaves the user vulnerable to 'cloudron uninstall' simply autoselecting this new app. For this, they have to simply disable CLI mode for now. There is also a corner case where: 1. Dev installs from app store 2. Dev compiles from source and updates on top of app store install with --app <id> 3. Dev find out that his installation has auto-updated the next day.
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:
curl https://s3.amazonaws.com/prod-cloudron-releases/installer.sh -o installer.sh
chmod +x installer.sh
./installer.sh <domain> <aws access key> <aws acccess secret> <backup bucket> <provider> <release sha1>