@kentonv kentonv released this Jul 9, 2018 · 2 commits to master since this release

Assets 3

v0.236 (2018-07-08)

  • Updated multiple stacks for compatibility with Debian stretch.
  • Added listkeys command to show which app keys are in your keyring.
  • Added ability to check vagrant-spk version with --version.
  • Fix bug where curl cannot be downloaded.
  • Fix bug caused by Vagrant version 2.0.3 and later.

@kentonv kentonv released this Mar 17, 2018 · 36 commits to master since this release

Assets 3

v0.230 (2018-03-17)

  • Now using Debian Contrib base image rather than a custom image.
  • Fixed various bitrot.
  • Other fixes, see git history.

@paulproteus paulproteus released this Sep 21, 2016 · 68 commits to master since this release

Assets 3

v0.186 (2016-09-21)

  • BUG FIX:
    • All stacks embedding MySQL now use /var/tmp for temporary storage. Thanks
      @FiloSottile for reporting a Piwik issue that enabled us to notice this problem
      and fix it for all future packages. Note that newly-created apps in these platform
      stacks (lemp, uwsgi) will clear the /var/tmp directory every time the grain

@paulproteus paulproteus released this Jun 8, 2016 · 83 commits to master since this release

Assets 3

v0.165 (2016-06-07)

    • vagrant-spk enter-grain was basically 100% broken in v0.164, with some extra breakage on
      Windows. This release fixes that. Huge thanks to @ocdtrekkie for testing, to find the

@paulproteus paulproteus released this May 27, 2016 · 94 commits to master since this release

Assets 3

v0.164 (2016-05-27)

  • New features:
    • Add "vagrant-spk enter-grain" so developers can get a shell within a running grain.
      Thanks @zarvox for extensive review.
    • Update example to refer to vm where necessary. Thanks @pgrm.
    • Update libvirt README to refer to vm where necessary. Thanks @techtonik.

@paulproteus paulproteus released this May 2, 2016 · 118 commits to master since this release

Assets 3

v0.161 (2016-05-02)

  • BUG FIX:
    • Fix typo in deprecation warning when running: vagrant-spk global-status. Thanks to @astraw for the pull request.
  • Usability refinement:
    • Going forward, pipe curl output through cat so that it is
      more aggressively buffered and Vagrant shows it on one line.
      See: #158 . Thanks to @ndarilek for the report.

v0.159 (2016-04-22)

  • BUG FIX:
    • "vagrant-spk setupvm" would reliably crash on Windows 10, and
      perhaps other Windows systems. Bug reported by hexx on IRC;
      fixed by Drew Fisher. Thanks to hexx for the report.

@paulproteus paulproteus released this Mar 29, 2016 · 135 commits to master since this release

Assets 3

v0.155 (2016-03-28)

  • Two big user-facing changes:
  • Docs improvements: Add a libvirt README to GitHub.
  • Usability refinements:
    • Network performance: Use PCNet-Fast III by default for virtual machines.
    • Error handling: exit(1) when specifying no stack to setupvm.
    • Interactive docs: 'vagrant-spk setupvm' now prints a list of known stacks.
    • Error handling: Stop crashing when user forgets filename for 'vagrant-spk publish'.
    • Default 'setup.sh' tells users they might need to re-run 'provision'.
    • Default apt configuration will retry on failure.
    • Provide a .sandstorm/.gitignore to avoid users committing useless cruft.
    • Support 'vagrant-spk keygen -- -q' for use by scripts.
    • Vagrantfile: Stop mounting '/vagrant' - this is a duplicate of /opt/app.
    • Python stack: install git by default, since pip/requirements.txt might need it.
    • Add PHP & sqlite stack, to minimize bloat for PHP apps that don't need MySQL.
    • Use 'rm -f' and 'ln -sf' for idempotence.
    • Set 'gzip off;' by default, to work around a Sandstorm bug that results
      in meaningless gobbledy-gook on error pages.

@paulproteus paulproteus released this Jan 14, 2016 · 191 commits to master since this release

Assets 3

v0.139 (2016-01-13)

  • New features:
    • Add nodejs stack by @mnutt.
    • Add vagrant-spk verify command by @zarvox.
    • In PHP configuration file, use semicolon as comment marker, not hash sign.
      If you run into PHP errors related to this problem, you may need to
      re-generate your .sandstorm/*.sh scripts, and destroy & recreate your
      Vagrant box. Thanks to @ndarilek for finding.

@paulproteus paulproteus released this Dec 16, 2015 · 203 commits to master since this release

Assets 3

v0.137 (2015-12-16)

  • BREAKING CHANGE: Every Sandstorm app MUST change one line in .sandstorm/Vagrantfile.
    • Change required: Every app must edit .sandstorm/Vagrantfile. Find the line containing:
      • config.vm.box = "debian/jessie64" and replace it with
      • config.vm.box = "sandstorm/debian-jessie64"
    • Problem: Debian's official Vagrant base box (aka debian/jessie64) has stopped
      supporting VirtualBox file sharing. Specifically, version 8.2.2 of their base box
      made this change. This will result in sadness for vagrant-spk users: anyone who
      runs vagrant-spk up on a new system will get version 8.2.2 of the debian/jessie64
      base box, resulting in non-working VirtualBox file sharing, resulting in apps that
      fail to build. If you've run vagrant box update, you may have also downloaded version
      8.2.2 of debian/jessie64, triggering the problem.
    • Solution: Sandstorm.io now maintains a
      separate Vagrant base box
      (called sandstorm/debian-jessie64) which does support VirtualBox file sharing.
      For now, this is a bit-for-bit copy of the most recent debian/jessie64 base box
      that did support file sharing. Since Sandstorm now controls the base box, it is
      safe to run vagrant box update once you have changed to our base box.
  • Update vagrant-spk up to check for the above problem and inform people on
    how to fix it. Update auto-generated Vagrantfile accordingly as well.
  • For freshly-created Meteor apps, be a little less quiet so that people can
    understand how their package build is progressing.
  • (EXPERIMENTAL) Improvements to automatic Meteor app packaging, aka
    vagrant-spk auto meteor:
    • Automatically switch Google Fonts from HTTP to HTTPS.
    • Open .meteor/ files in append mode, to avoid overwriting them.
    • Add more newlines when editing .meteor/ files.

@paulproteus paulproteus released this Nov 4, 2015 · 233 commits to master since this release

Assets 3

v0.130 (2015-11-04)

  • (EXPERIMENTAL) vagrant-spk auto meteor improvements:
    • Automatically switch (some) HTTP resource references to HTTPS.
    • Add kentonv:accounts-sandstorm to generated packages.
    • Use git repo name to infer package name.
    • Store git repo URL in the package metadata.
  • Meteor stack: Use meteor-spk version 0.1.8. This fixes a bug where
    niscudb => Mongo 3 migrations would sometimes fail. If your app has
    PACKAGE=meteor-spk-0.1.7 in .sandstorm/setup.sh, and if it
    ever had a previous version, then you should migrate to
    PACKAGE=meteor-spk-0.1.8 and do vagrant-spk destroy to flush the
    cached meteor-spk package version in any packaging VMs.