Talk:MediaWiki-Vagrant: Difference between revisions

From mediawiki.org
Latest comment: 10 years ago by Nemo bis in topic Time for first vagrant up
Content deleted Content added
Line 12: Line 12:


"vagrant up" fails for me, complaining that my version of VirtualBox is too new (it wants 4.0-4.2, and Debian unstable has 4.3.2). Sigh. [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 18:02, 23 January 2014 (UTC)
"vagrant up" fails for me, complaining that my version of VirtualBox is too new (it wants 4.0-4.2, and Debian unstable has 4.3.2). Sigh. [[User:Anomie|Anomie]] ([[User talk:Anomie|talk]]) 18:02, 23 January 2014 (UTC)

== Time for first vagrant up ==

I've changed 10-15 min to about a hour, because 10-15 min is just the time for the download of the Ubuntu image on a 5? Mb/s connection. However, I think two hours would be more realistic:
notice: Finished catalog run in 5756.80 seconds
In my first "vagrant up", with most time spent after
notice: /Stage[main]/Git/Package[git]/ensure: ensure changed 'purged' to 'latest'
and before
notice: /Stage[main]/Mediawiki/Git::Clone[mediawiki/core]/Exec[git clone mediawiki/core]/returns: executed successfully
for a total of 129 minutes of CPU time. Nothing tragic, but had I known I would only have started it before going to bed. --[[User:Nemo_bis|Nemo]] 07:50, 22 February 2014 (UTC)

Revision as of 07:50, 22 February 2014

Labs dependencies?

Mostly just a note to self, things to research and add to the documentation:

  • First run does not seem to work for me, puppet never runs. After destroying that box, the next call to "vagrant up" succeeds. Something to do with the order of linking or shared directories?
  • The redis-server puppet module specifies a "-wmf" package, thus will not work without setting up WMF apt sources.
  • Configuring a redis object cache might be a bit heavy for the default install?

Adamw (talk) 03:43, 12 November 2013 (UTC)Reply

that port 8080 appears to be taken on my machine ... where is the file to change the port?

Versioning, sigh

"vagrant up" fails for me, complaining that my version of VirtualBox is too new (it wants 4.0-4.2, and Debian unstable has 4.3.2). Sigh. Anomie (talk) 18:02, 23 January 2014 (UTC)Reply

Time for first vagrant up

I've changed 10-15 min to about a hour, because 10-15 min is just the time for the download of the Ubuntu image on a 5? Mb/s connection. However, I think two hours would be more realistic:

notice: Finished catalog run in 5756.80 seconds

In my first "vagrant up", with most time spent after

notice: /Stage[main]/Git/Package[git]/ensure: ensure changed 'purged' to 'latest'

and before

notice: /Stage[main]/Mediawiki/Git::Clone[mediawiki/core]/Exec[git clone mediawiki/core]/returns: executed successfully

for a total of 129 minutes of CPU time. Nothing tragic, but had I known I would only have started it before going to bed. --Nemo 07:50, 22 February 2014 (UTC)Reply