Last modified: 2014-09-29 23:07:58 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 T72304, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 70304 - .settings.yaml is loaded from CWD instead of mw-vagrant root


Summary:	.settings.yaml is loaded from CWD instead of mw-vagrant root

Status:	RESOLVED FIXED

Product:	MediaWiki-Vagrant
Classification:	Unclassified
Component:	General (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nobody - You can work on this!

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-09-02 22:08 UTC by Erik Bernhardson
Modified:	2014-09-29 23:07 UTC (History)
CC List:	4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Erik Bernhardson 2014-09-02 22:08:22 UTC

My .settings.yaml includes:

    vagrant_ram: 4096

If i `vagrant up` from the mediawiki-vagrant directory this gets applied, but if I run `vagrant up` from any subdirectory from within mediawiki-vagrant this setting is not loaded and i get 1G of memory.

afaict the code is prefering a :root_path environment variable over cwd, but it seems rather than defaulting to cwd it should default to the same directory as the Vagrantfile

Comment 1 Bryan Davis 2014-09-26 15:50:26 UTC

Nik attempted to fix this bug in https://gerrit.wikimedia.org/r/#/c/159333/. Can you retest and see if you still have this problem?

Comment 2 Erik Bernhardson 2014-09-29 23:07:58 UTC

appears fixed now, thanks!

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links