diff options
| author | jakefeasel <jfeasel@gmail.com> | 2015-06-07 13:38:55 -0700 |
|---|---|---|
| committer | jakefeasel <jfeasel@gmail.com> | 2015-06-07 13:38:55 -0700 |
| commit | 1475c9cc08d13edbe4a67160cc8067d8dc8f8ba9 (patch) | |
| tree | 1d10acc58fbc9dd55e1fdc18ad4f761e525e5b72 | |
| parent | 7d1bf51439b1fb1a35557ac9b696426cbc2df9e3 (diff) | |
| download | sqlfiddle2-1475c9cc08d13edbe4a67160cc8067d8dc8f8ba9.zip sqlfiddle2-1475c9cc08d13edbe4a67160cc8067d8dc8f8ba9.tar.gz sqlfiddle2-1475c9cc08d13edbe4a67160cc8067d8dc8f8ba9.tar.bz2 | |
Better details for setting up the site in AWS
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -53,4 +53,8 @@ To run the commercial database software (Microsoft SQL Server 2014 Express, Orac With a bit of preparation, you should be able to deploy the whole app into Amazon Web Services. See the comments in Vagrantfile for an example config that you can fill in with your own AWS account details. For MS SQL and Oracle support, you will have to create your own AMI with Windows, following the same steps mentioned above. +You will need to install the vagrant-aws plugin. See the plugin site here for details: https://github.com/mitchellh/vagrant-aws + +Be sure to also install the "dummy" box. + You may also wish to have automated backups of your sqlfiddle database to S3. If so, you will need to add a .s3cfg file under vagrant_scripts. This file will not be added to the git repo (it is ignored) but if present the PostgreSQL server will automatically schedule backups to write to your account. The .s3cfg file is produced by "s3cmd" - check this site for more details: http://s3tools.org/s3cmd-howto
\ No newline at end of file |