Ticket #1116 (open enhancement)
support readonly PUN_ROOT
- Created: 2018-07-07 21:46:39
- Reported by: root_hippyru
- Assigned to: None
- Milestone: 1.6
- Component: installation
- Priority: normal
Currently it is rather non-trivial to use fluxbb when PUN_ROOT is read-only. For example, one may want to install fluxbb as root or under a read-only mount path as a part of system installation. But then one has a problem as fluxbb assumes that it can write to PUN_ROOT/config.php and PUN_ROOT/img/avatars and that it can remove PUN_ROOT/install.php.
One can work-around this by using symlinks or bind-mounts to point files and directories to a writable location. But this is problematic.
First it complicates the updates as one needs to remember to restore symlinks after the update. Second it may lead to spurious alerts about non-writable directories during installation or a warning about install.php that should be deleted. Third it is impossible to share the same installation between different forums or forum running against slightly different config.php which is often useful during development or debugging.
So it would be nice to have an explicit support for read-only PUN_ROOT.
Franz 2018-07-08 21:26:06
First of all, thanks for the suggestion and your pull request!
Before we get into the solution space, can we talk about the problem a bit more? Using the files of FluxBB for multiple running instances is what you are trying to achieve? The other points ("First", "second", ...) are just side-effects, right?
root_hippyru 2018-07-08 22:42:20
My primary objective is a read-only installation as a root that should only be updated as a part of a system update or a read-only Docker container. As fluxbb cannot change its files, it makes things more secure. The multiple installations is just a useful consequence of that.
Franz 2018-07-09 21:13:51
Ah, okay, cheers. Will review your PR with that in mind.
Franz 2018-07-18 09:20:40
- Milestone set to 1.6.