Hello,
I'm writing to tell you about some cool new MediaWiki-Vagrant features. MediaWiki-Vagrant now ships with a custom Vagrant plug-in that augments the default 'vagrant' command-line tool with some additional sub-commands that are specifically designed to make MediaWiki development more productive and fun.
The most important addition is a set of four sub-commands for managing roles. (Roles, you'll recall, are optional software stacks that MediaWiki-Vagrant can configure automatically. There's a VisualEditor role, a Scribunto role, a qa/browsertests role, etc.) The new commands are:
$ vagrant list-roles Lists available roles. Currently enabled roles are marked with a '*'.
$ vagrant enable-role Enables a role. Example: 'vagrant enable-role visualeditor'.
$ vagrant disable-role <name> Disables a role.
$ vagrant reset-roles Disable all roles.
There's a short, 1-minute screencast up at http://ascii.io/a/4428demonstrating usage. Check it out. I'll wait.
The other cool sub-command that was recently added is 'vagrant run-tests'. Any command-line arguments following 'run-tests' are passed through to PHPUnit running on the VM, so it's possible to run (for example) 'vagrant run-tests extensions/EventLogging'. Finally, there's 'vagrant puppet-paste'. This uploads the log of your most recent Puppet run to < dpaste.de> and prints out a URL. This is primarily intended as a debugging aid.
Additional documentation, including installation help, is up at < https://www.mediawiki.org/wiki/MediaWiki-Vagrant%3E. Please report any bugs you encounter at < https://bugzilla.wikimedia.org/enter_bug.cgi?product=Tools&component=Vag...
.
Ori
Le 30/07/13 06:39, Ori Livneh a écrit :
There's a short, 1-minute screencast up at http://ascii.io/a/4428demonstrating usage. Check it out. I'll wait.
I am sorry to report you are definitely too awesome. Thank you for all your work on that front \O/
Awesome!!! Thanks Ori!!!
Can we have varnish through a role please? We will have to do a lot of dev & test for it soon.
The default varnish config in /etc/varnish/default.vcl could have this at the very top of the file. Leave all comments there.
backend default { .host = "127.0.0.1"; .port = "80"; }
start with:
sudo varnishd -f /etc/varnish/default.vcl -s malloc,1G -T 127.0.0.1:2000 -a 0.0.0.0:8080
This way varnish will only work if accessed through port 8080 (needs to be mapped to outside), while port 80 will continue be served uncached. The admin port 2000 doesn't have to be patched to the outside (rarely used, can be accessed through ssh).
P.S. Note that varnish config should not be deleted on every vagrant up - there could be a lot of changes during development to that file. Maybe it would make sense to have an include command of some sort the same way as settings.d/ files for vagrant.
Thanks!
On Tue, Jul 30, 2013 at 4:58 AM, Antoine Musso hashar+wmf@free.fr wrote:
Le 30/07/13 06:39, Ori Livneh a écrit :
There's a short, 1-minute screencast up at http://ascii.io/a/4428demonstrating usage. Check it out. I'll wait.
I am sorry to report you are definitely too awesome. Thank you for all your work on that front \O/
-- Antoine "hashar" Musso
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Ori I have a quick question.
Would there be any way to have a quick method of switching PHP versions, specifically for testing purposes? Like "vagrant enable-role php5.4" or maybe it'd have it's own command.
That way it's easy to test compatibility with other versions.
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerromeo@gmail.com
On Tue, Jul 30, 2013 at 12:51 PM, Yuri Astrakhan yastrakhan@wikimedia.orgwrote:
Awesome!!! Thanks Ori!!!
Can we have varnish through a role please? We will have to do a lot of dev & test for it soon.
The default varnish config in /etc/varnish/default.vcl could have this at the very top of the file. Leave all comments there.
backend default { .host = "127.0.0.1"; .port = "80"; }
start with:
sudo varnishd -f /etc/varnish/default.vcl -s malloc,1G -T 127.0.0.1:2000-a 0.0.0.0:8080
This way varnish will only work if accessed through port 8080 (needs to be mapped to outside), while port 80 will continue be served uncached. The admin port 2000 doesn't have to be patched to the outside (rarely used, can be accessed through ssh).
P.S. Note that varnish config should not be deleted on every vagrant up - there could be a lot of changes during development to that file. Maybe it would make sense to have an include command of some sort the same way as settings.d/ files for vagrant.
Thanks!
On Tue, Jul 30, 2013 at 4:58 AM, Antoine Musso hashar+wmf@free.fr wrote:
Le 30/07/13 06:39, Ori Livneh a écrit :
There's a short, 1-minute screencast up at http://ascii.io/a/4428demonstrating usage. Check it out. I'll wait.
I am sorry to report you are definitely too awesome. Thank you for all your work on that front \O/
-- Antoine "hashar" Musso
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Jul 30, 2013 at 9:58 AM, Tyler Romeo tylerromeo@gmail.com wrote:
Would there be any way to have a quick method of switching PHP versions, specifically for testing purposes? Like "vagrant enable-role php5.4" or maybe it'd have it's own command.
On Tue, Jul 30, 2013 at 12:51 PM, Yuri Astrakhan yastrakhan@wikimedia.orgwrote:
Can we have varnish through a role please? We will have to do a lot of
dev
& test for it soon.
Both of these requests sound reasonable. Can you file bugs (severity: enhancement) in BZ?
Hi Ori,
Is there a reason for having Guest Additions Version 4.1.12 in the VM instead of 4.2?
$ vagrant up (...) [default] VM booted and ready for use! [default] The guest additions on this VM do not match the installed version of VirtualBox! In most cases this is fine, but in rare cases it can cause things such as shared folders to not work properly. If you see shared folder errors, please update the guest additions within the virtual machine and reload your VM.
Guest Additions Version: 4.1.12 VirtualBox Version: 4.2 [default] Setting hostname... (...)
I will file a bug in Bugzilla if that is something you can fix.
Željko
On Thu, Sep 26, 2013 at 1:52 AM, Željko Filipin zfilipin@wikimedia.orgwrote:
Hi Ori,
Is there a reason for having Guest Additions Version 4.1.12 in the VM instead of 4.2?
It's what Canonical's Vagrant image provides, and it's because that's the version that is packaged for Precise. (Remember, guest additions run on the guest.) You can update to the latest version by running 'update-guest-additions' in the VM.
I'll take the opportunity to remind folks who use Vagrant to send some positive feedback to Canonical. The Vagrant image they provide is part of a beta program they have not yet committed to supporting permanently.
Per http://blog.utlemming.org/2013/01/vagrant-cloud-images.html "For those who use Vagrant, your feedback is essential. Please feel free to send feedback via the ubuntu-cloud@lists.ubuntu.com mailing list."
wikitech-l@lists.wikimedia.org