h2
Friday, September 25, 2015
h2
Thursday, August 6, 2015
h2
Monday, November 13, 2017
h2
Thursday, October 19, 2017
h2
Wednesday, June 28, 2017
h2
Tuesday, October 20, 2015
h2
Friday, October 16, 2015
h3
Vagrant on AWS with Windows
h3
Local Vagrant VM as part of a deployment strategy
h3
Georeference a non-referenced image with gdal_translate
h3
Solution, Geoserver bug with authenticated requests
h3
Geoserver WFS-T PostGIS (PostgreSQL) Layer Read-Only
h3
Out to ride -- back sometime in September
h4
(1) Create the directory for the new Vagrant configuration files – I will call mine vagrant-local mk
h4
(2) Create a new vagrantfile, using your favorite text editor (e.g., vi vagrantfile) and insert the
h4
(3) Save this file, and bring the vagrant VM vagrant up
h4
(4) As you install packages, make sure to add those lines to a new file, (vi bootstrap.sh). You can
h4
(5) Uncoment line second to end (config.vm.provision :shell, path: "bootstrap.sh") in your vagrantfi
h4
(6) Destroy the existing vagrant instance, including all files created when you brought it up vagran
h4
(1) Use the AWS CLI/Security Token Service to generate temporary credentials for AWS
h4
(2) Install the Vagrant AWS plugin.
h4
(3) Add the “dummy” Box provided by the vagrant-aws project. This is a barebones Box compatible with
h4
(4) Create a new directory to hold files for this Vagrant instance. I’m calling this vagrant-aws.
h4
(5) With your favorite text editor create a file called Vagrantfile inside this new directory. Edit
h4
(6) Now edit this text with the credentials returned by AWS STS (from above). You can use a differen
h4
(7) Now you can bring the instance up with Vagrant, first making sure you are in the directory where