History

Fixes #9840 : Introduce ruby option for trigger

This commit introduces a new option to the core trigger feature: `ruby`.
It can be defined to run ruby code when the trigger is configured to
fire. If you give the ruby block an env and machine argument, the
defined ruby code can use those variables internally.

2018-10-05 12:53:41 -07:00

scripts

Update deploy process

2017-08-02 14:13:58 -04:00

source

Fixes #9840 : Introduce ruby option for trigger

2018-10-05 12:53:41 -07:00

config.rb

Update website version 2.1.5

2018-09-12 08:45:01 -07:00

Gemfile

switch web analytics from ga to segment

2018-04-06 18:25:11 -04:00

Gemfile.lock

switch web analytics from ga to segment

2018-04-06 18:25:11 -04:00

LICENSE.md

Update license

2017-03-08 11:39:24 -08:00

Makefile

switch web analytics from ga to segment

2018-04-06 18:25:11 -04:00

packer.json

switch web analytics from ga to segment

2018-04-06 18:25:11 -04:00

README.md

website/README: Add a link to CONTRIBUTING.md

2018-05-16 14:26:14 +02:00

redirects.txt

Update deploy process

2017-08-02 14:13:58 -04:00

README.md

Vagrant Website

This subdirectory contains the entire source for the Vagrant Website. This is a Middleman project, which builds a static site from these source files.

Contributions Welcome!

If you find a typo or you feel like you can improve the HTML, CSS, or JavaScript, we welcome contributions. Feel free to open issues or pull requests like any normal GitHub project, and we'll merge it in.

See also the Vagrant Contributing Guide for more details.

Running the Site Locally

Running the site locally is simple. Clone this repo and run make website.

Then open up http://localhost:4567. Note that some URLs you may need to append ".html" to make them work (in the navigation).