You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
linux-app should use $XDG_CONFIG_HOME and $HOME/.config to save everything that requires write access.
How important this is to me and why
Importance: High
Use cases:
Distribute as a package
Per-user config and database
Additional context/similar features
I've spent some time working on packaging focalboard into the following formats: rpm, deb, flatpak
While everything is going as planned there's a major issue; apps don't have write access to their installed location by default (in focalboard's case, /opt/focalboard-app).
While there might be workarounds, the best practice would be to move anything that requires write access to .config (dbconfig & filespath (?)). Doing so will also allow each user to have their own .db as well as ease backups and restores.
From a look at the source, it seems that config.json is being ignored (for the app at least).
Here's some solutions I came up with:
Use the values from the config.json in combination with the hardcoded ones.
while I mostly agree, $XDG_CONFIG_HOME (i.e. ~/.config) is for configuration files whereas $XDG_DATA_HOME (i.e. ~/.local/share) is where applications store state.
Though there are applications that ignore this and use config home for both, (vscode and obsidian come to mind). I'd definitely appreciate following spec though.
Summary
linux-app should use
$XDG_CONFIG_HOME
and$HOME/.config
to save everything that requires write access.How important this is to me and why
Importance: High
Use cases:
Additional context/similar features
I've spent some time working on packaging focalboard into the following formats: rpm, deb, flatpak
While everything is going as planned there's a major issue; apps don't have write access to their installed location by default (in focalboard's case,
/opt/focalboard-app
).While there might be workarounds, the best practice would be to move anything that requires write access to
.config
(dbconfig
&filespath
(?)). Doing so will also allow each user to have their own .db as well as ease backups and restores.From a look at the source, it seems that
config.json
is being ignored (for the app at least).Here's some solutions I came up with:
~/.config
Some notes on them:
After a solution to this is found, I'll be able to continue working on packaging focalboard in more formats (rpm, deb, flatpak, appimage, snap).
The text was updated successfully, but these errors were encountered: