Last modified: 2013-09-11 22:46:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48676, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46676 - Provide Vagrant subcommand(s) for common MediaWiki maintenance tasks
Provide Vagrant subcommand(s) for common MediaWiki maintenance tasks
Status: RESOLVED FIXED
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Ori Livneh
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-29 00:41 UTC by Ori Livneh
Modified: 2013-09-11 22:46 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2013-03-29 00:41:43 UTC
It would be nice to be able to do things like trigger test runs or restart Apache without having to first SSH into the host. Vagrant provides hooks for plug-ins to add sub-commands. Having a MediaWiki plug-in that allows common tasks to be run from the host would be nice.
Comment 1 Daniel Friesen 2013-03-30 18:23:55 UTC
Currently this has to be done in a global way. Individual vagrant projects can't define custom plugins. Only plugins from the global rubygems (the ones bundled with vagrant included) and plugins installed in a .vagrant/gems home folder (presumably managed by `vagrant plugin`) can be loaded.

Would be a little ugly for vagrant to list `vagrant mwupdate
Comment 2 Daniel Friesen 2013-03-30 18:28:25 UTC
Currently this has to be done in a global way. Individual vagrant projects can't define custom plugins. Only plugins from the global rubygems (the ones bundled with vagrant included) and plugins installed in a .vagrant/gems home folder (presumably managed by `vagrant plugin`) can be loaded.

Would be a little ugly for vagrant to list `vagrant mwupdate`, `vagrant mwreset`, etc... when you list the vagrant commands and aren't in a project related to MediaWiki at all.

While it's not possible now. Looking at the vagrant code. In theory by making some changes to lib/vagrant/environment.rb:load_plugins it should be possible to make it so future versions of vagrant permit individual vagrant projects to define custom vagrant plugins that are only loaded when inside the project.
Comment 3 Ori Livneh 2013-07-14 22:04:41 UTC
(In reply to comment #2)
> Currently this has to be done in a global way. Individual vagrant projects
> can't define custom plugins.

Not true, actually: you can use require / require_relative your plug-in from the Vagrantfile.
Comment 4 Gerrit Notification Bot 2013-07-14 22:09:00 UTC
Change 73714 had a related patch set uploaded by Ori.livneh:
Run MediaWiki unit tests via 'vagrant run-tests'

https://gerrit.wikimedia.org/r/73714
Comment 5 Gerrit Notification Bot 2013-07-14 22:36:45 UTC
Change 73714 merged by jenkins-bot:
Run MediaWiki unit tests via 'vagrant run-tests'

https://gerrit.wikimedia.org/r/73714
Comment 6 Ori Livneh 2013-07-14 23:20:18 UTC
Closing as resolved. There are a few more sub-commands I'd like to add, but the scaffolding is there now.
Comment 7 Andre Klapper 2013-09-11 22:46:01 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links