mahara-contributors team mailing list archive

[Hugh Davenport <780177@xxxxxxxxxxxxxxxxxx>]

Had a crazy thought. It could be done by doing this.

If not in config.php, autogen and try to write back to config.php (if it is writeable by www-data)
Don't put in db

Then when people need to change site, they change in config.php

This means the autogen should only happen once, users only have to
modify changes in one place (or can remove the entry in config.php to
get autogen to trigger again)

The downside, if config.php isn't writable, then the autogen will
trigger for every request.

Cheers,

Hugh

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/780177

Title:
  Storing wwwroot in the database: possible implications

Status in Mahara ePortfolio:
  New

Bug description:
  Basically this issue comes from bug #684190. Are there any
  implications of impossibility to change wwwroot once it is stored in
  the database? In the hostname change wiki manual we suggest people to
  clear this variable manually in the database which is somewhat
  complicated. In addition, protocol changes (upgrade to using https or
  downgrade to http) might not be considered as hostname change by the
  user, so database config variable will be left in inconsistent state.

  Do we need to keep it in the database for specific reason (e.g.
  comment says it used by cron, I did not quickly find where exactly)?