haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4,677 Commits 8 Branches 143 Tags 51 MiB
Commit Graph

113 Commits

Author SHA1 Message Date
Mitchell Hashimoto 36f64db874 Always setup plugins, but just don't always require them 2014-01-05 16:49:25 -08:00
Mitchell Hashimoto f7e4c4df6b setup the Bundler path always 2014-01-05 16:43:59 -08:00
Mitchell Hashimoto 8861510520 Lower some branching logic 2014-01-05 16:17:39 -08:00
Mitchell Hashimoto 73c71dbcc6 Work some things around so that Bundler is not setup with no plugins 2014-01-05 16:16:04 -08:00
Mitchell Hashimoto 76de267d1e Don't load plugins again on `vagrant plugin` commands 2014-01-05 16:04:53 -08:00
Mitchell Hashimoto 8cfa24143d Put plugins in their own Gemfile group so we can load on their own 2014-01-05 15:57:10 -08:00
Mitchell Hashimoto e800743d06 fast-path vagrant --version 2014-01-05 15:32:19 -08:00
Mitchell Hashimoto 817f7f326e fast path Vagrant --version 2014-01-05 15:27:03 -08:00
Mitchell Hashimoto 91751f6e41 load with bundler context 2014-01-05 15:26:44 -08:00
Mitchell Hashimoto 8adef9c15f warn if running in a bundler env, don't load plugins 2014-01-04 16:29:22 -08:00
Erik Michaels-Ober 56175b8132 Replace `exit 1` with `abort` 
According to the documentation, Kernel.abort calls Kernel.exit(false). The failure status 1 is an implementation detail on Unix-like systems. In theory, a future system could exist where 1 indicates a successful exit and 0 indicates a failure.
 2014-01-03 17:32:45 +01:00
Mitchell Hashimoto 3219be3d51 core: only look for global flags before "--" [GH-2491] 2013-11-25 11:42:06 -08:00
Mitchell Hashimoto f861fbcafb Update CHANGELOG 2013-11-24 11:58:06 -08:00
Mitchell Hashimoto 0c19578afa Merge pull request #2261 from mrkafk/master 
core: check ENV for VAGRANT_NOCOLOR (equivalent of --no-color on cmdline)
 2013-11-24 11:57:16 -08:00
Mitchell Hashimoto 42a71a953d commands/status: add machine-readable output 2013-11-24 11:11:38 -08:00
Mitchell Hashimoto c5a7ab7953 core: Add the MachineReadable UI, --machine-readable flag 2013-11-24 11:04:54 -08:00
Mitchell Hashimoto de9d38de21 core: don't load vagrantfile on plugin command 2013-11-23 13:25:33 -08:00
Teemu Matilainen 28740943bb Add `--debug` option as a shortcut for `VAGRANT_LOG=debug` 
When asking or submitting debug information, a command line switch is
easier and faster than using an environment variable.
 2013-10-31 22:20:13 -03:00
Mitchell Hashimoto eb6256316c core: improved commenting in bin/vagrant 2013-10-23 23:20:27 -07:00
root e4b6c91b7c check ENV for VAGRANT_NOCOLOR (equivalent of --no-color on cmdline) 2013-09-23 19:21:51 +02:00
Greg Poirier f65f2d20d9 Remove 'v' prefix on version number in vagrant -v 2013-09-06 11:14:17 -07:00
Mitchell Hashimoto 896ae7b9ba core: vagrant -v no longer loads Vagrantfile 2013-09-02 15:43:59 -07:00
Mitchell Hashimoto 7c9219fc18 Add --color to force color output [GH-2027] 2013-08-09 11:40:08 -07:00
Mitchell Hashimoto 5ca89383f8 Simplify cygwin check everywhere 2013-04-06 16:05:13 -07:00
Mitchell Hashimoto fb9c311b4d Always colorize Cygwin output 2013-04-06 16:03:25 -07:00
Mitchell Hashimoto b32c0d16ac Better plugin dev experience through warnings 2013-03-28 17:10:07 -07:00
Mitchell Hashimoto 9c7bedfb63 Always unload the environment 2013-03-03 00:09:40 -08:00
Mitchell Hashimoto 2b37185994 Don't load plugins when using the `vagrant plugin` interface 2013-02-28 22:32:13 -08:00
Mitchell Hashimoto 46db50680b environment_unload hook 2013-02-22 13:54:28 -08:00
Mitchell Hashimoto 0d27cd5bcb Warn if Vagrant is run outside of installers 2013-01-28 13:39:56 -08:00
Mitchell Hashimoto a50539bc78 Remove the development version warning 2013-01-28 12:44:24 -08:00
Mitchell Hashimoto a4713d5a84 No need to call `load!` anymore, since it doesn't exist 2012-12-23 16:29:23 -08:00
Mitchell Hashimoto de73b65635 Very early SIGINTs no longer cause ugly stack traces. 
We catch INT very very early in the Vagrant process in order to exit
cleanly rather than raising any exceptions. This is eventually overriden
by Vagrant at some point.
 2012-08-10 00:30:58 -07:00
Sean Coates d6249f671d folder is ~/.vagrant.d not ~/vagrant.d 2012-07-26 10:57:20 -04:00
Mitchell Hashimoto 141dccd4e7 Modify warning message to be more clear [GH-1027] 2012-07-16 09:49:04 -07:00
Mitchell Hashimoto c634cbedcc Handle interrupts more gracefully on the warning message 2012-07-11 18:47:41 -07:00
Mitchell Hashimoto 933b0b3101 Clarify that the warning will be removed when official version is 
released
 2012-07-11 18:34:36 -07:00
Mitchell Hashimoto e92fbb4d33 Add backwards incompatibility warning. 2012-07-11 18:28:08 -07:00
Mitchell Hashimoto 3338b6c134 Support arbitrary exit statuses for CLI commands that aren't exploding 2012-03-23 11:07:35 -04:00
Mitchell Hashimoto 97235ee080 Clean up some impl [GH-666] 2012-01-20 11:25:39 -08:00
Jarmo Pertman b9046a5594 enable colors on Windows when using ANSICON 2012-01-20 11:21:16 -08:00
Mitchell Hashimoto 8a0e81276e Don't output color on Windows, since the default terminal doens't support it 2012-01-05 23:03:20 -08:00
Mitchell Hashimoto 1dd41cfef4 Delete "--no-color" from arguments if it is given 2011-12-18 14:00:27 -08:00
Mitchell Hashimoto 27491b554c Remove thor from requirements. Start revamping Vagrant::CLI 2011-12-16 23:34:30 -08:00
Mitchell Hashimoto d9e2c8b788 Raise a nice error if home directory is not accessible 2011-12-10 17:14:07 -08:00
Mitchell Hashimoto 5cf0c527a3 Do not buffer stdout/stderr 2011-12-10 13:44:34 -08:00
Mitchell Hashimoto fe65dd0dd5 Remove VAGRANT_DEBUG. 
VAGRANT_LOG handles it all now.
 2011-12-03 17:16:49 -08:00
Mitchell Hashimoto e38e3cc652 Move VAGRANT_LOG logic into vagrant.rb so VAGRANT_LOG is always available 2011-12-03 17:12:07 -08:00
Mitchell Hashimoto 271d1a92f0 Allow enabling of logging with VAGRANT_LOG 2011-12-03 16:11:31 -08:00
Mitchell Hashimoto 1355487a04 Environment UI class can now be set through the environment init 2011-12-03 16:07:34 -08:00