mirror of
https://github.com/freedombox/FreedomBox.git
synced 2026-01-28 08:03:36 +00:00
cfg: In develop mode, use /var/lib for DB and sessions
- Only effects develop mode. - To primarily avoid writing to the source code directory. Multiple containers or VMs using the source folder won't fight with the database file (the overlay file system plan is not working out well for containers #1873). - In the earlier days, we used to allow running from source code directory without even doing ./setup.py install. Currently it is not possible anyway. We pretty much install freedombox package before running from source directory. - If the build process itself learns not to write to source directory, then containers/VMs won't have to write to source directory at all. Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org> Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
This commit is contained in:
parent
a2281aaf07
commit
91c4d6742e
22
container
22
container
@ -47,16 +47,15 @@ Shared folder: Using systemd-nspawn, the project directory is mounted as
|
||||
/freedombox inside the container. The project directory is determined as
|
||||
directory in which this script resides. The project folder from the container
|
||||
point of view will be read-only. Container should be able to write various
|
||||
files such as build files, FreedomBox sqlite3 database and session files into
|
||||
the /freedombox folder. To enable writing, an additional read-write folder is
|
||||
overlayed onto /freedombox folder in the container. This directory can't be
|
||||
created under the project folder and is created instead in
|
||||
$XDG_DATA_HOME/freedombox-container/overlay/$DISTRIBUTION. If XDG_DATA_HOME is
|
||||
not set, it is assumed to be $HOME/.local/shared/. Whenever data is written
|
||||
into /freedombox directory inside the container, this directory on the host
|
||||
receives the changes. See documentation for Overlay filesystem for further
|
||||
details. When container is destroyed, this overlay folder is destroyed to
|
||||
ensure clean state after bringing up the container again.
|
||||
files such as build files into the /freedombox folder. To enable writing, an
|
||||
additional read-write folder is overlayed onto /freedombox folder in the
|
||||
container. This directory can't be created under the project folder and is
|
||||
created instead in $XDG_DATA_HOME/freedombox-container/overlay/$DISTRIBUTION.
|
||||
If XDG_DATA_HOME is not set, it is assumed to be $HOME/.local/shared/. Whenever
|
||||
data is written into /freedombox directory inside the container, this directory
|
||||
on the host receives the changes. See documentation for Overlay filesystem for
|
||||
further details. When container is destroyed, this overlay folder is destroyed
|
||||
to ensure clean state after bringing up the container again.
|
||||
|
||||
Users: PrivateUsers configuration flag for systemd-nspawn is currently off.
|
||||
This means that each user's UID on the host is also the same UID in the
|
||||
@ -138,9 +137,6 @@ KEY_SERVER = 'keys.gnupg.net'
|
||||
PROVISION_SCRIPT = '''
|
||||
set -x
|
||||
|
||||
# Remove FreedomBox database lingering in source directory to start fresh
|
||||
sudo rm -f /freedombox/data/var/lib/plinth/plinth.sqlite3
|
||||
|
||||
cd /freedombox/
|
||||
|
||||
sudo apt-get update
|
||||
|
||||
@ -1,8 +1,5 @@
|
||||
[Path]
|
||||
file_root = %(parent_parent_dir)s
|
||||
config_dir = %(file_root)s/data/etc/plinth
|
||||
data_dir = %(file_root)s/data/var/lib/plinth
|
||||
actions_dir = %(file_root)s/actions
|
||||
doc_dir = %(file_root)s/doc
|
||||
custom_static_dir = %(file_root)s/data/var/www/plinth/custom/static
|
||||
store_file = %(data_dir)s/plinth.sqlite3
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user