etc/scripts: remove use of to AWS_* variables

Author: borsboom

etc/scripts/README.md

@@ -23,13 +23,6 @@ To create a signed binary package, you need:
   [msysgit](https://msysgit.github.io) on Windows)
 - `[email protected]` secret key in GPG keyring.
 
-To create signed Windows executables, you also need:
-
-- `signtool.exe`, which is installed with the
-  [Windows SDK](http://microsoft.com/en-us/download/confirmation.aspx?id=8279).
-- "FP Complete, Corporation" code signing key installed. See
-  [instructions for creating one with StartSSL](https://forum.startcom.org/viewtopic.php?p=5480&sid=143a360f30427e979f6c5b05c2df82cc#p5480).
-
 To upload a binary to a Github release, you also need:
 
 - A [Github authorization token](https://github.com/settings/tokens) with
@@ -39,24 +32,6 @@ To upload a binary to a Github release, you also need:
   (probably as a draft) with a tag for the stack package's version (e.g.
   `vX.Y.Z`).
 
-To create and upload Debian/Ubuntu packages, you need:
-
-- deb-s3 installed (`sudo gem install deb-s3`).
-- `[email protected]` secret key in GPG keyring.
-- Set `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment variables with
-  credentials that allow uploading to download.fpcomplete.com S3 bucket.
-
-To create and upload Red Hat/CentOS packages, you need:
-
-- [rpm-s3 installed](https://github.com/crohr/rpm-s3).
-- `[email protected]` secret key in GPG keyring.
-- Set `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment variables with
-  credentials that allow uploading to download.fpcomplete.com S3 bucket.
-
-To create and upload Arch packages, you need:
-
-- [AWS CLI installed](http://docs.aws.amazon.com/cli/latest/userguide/installing.html).
-
 Invocation
 ----------
 

etc/scripts/with-vagrant.sh

@@ -13,5 +13,5 @@ vagrant up
 
 vagrant provision
 vagrant rsync
-vagrant ssh -c "set -xe; $3 export GITHUB_AUTH_TOKEN=$GITHUB_AUTH_TOKEN; export AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID; export AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY; export AWS_DEFAULT_REGION=$AWS_DEFAULT_REGION; export AWS_SESSION_TOKEN=$AWS_SESSION_TOKEN; gpg --import /vagrant/gpg-secret-key.asc~ || true; cd /vagrant-build; for x in CONTRIBUTING ChangeLog; do rm -f doc/\$x.md; ln -s ../\$x.md doc/\$x.md; done; stack /vagrant/etc/scripts/release.hs --no-test-haddocks $2"
+vagrant ssh -c "set -xe; $3 export GITHUB_AUTH_TOKEN=$GITHUB_AUTH_TOKEN; gpg --import /vagrant/gpg-secret-key.asc~ || true; cd /vagrant-build; for x in CONTRIBUTING ChangeLog; do rm -f doc/\$x.md; ln -s ../\$x.md doc/\$x.md; done; stack /vagrant/etc/scripts/release.hs --no-test-haddocks $2"
 vagrant halt || vagrant halt -f