-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[log] Default log path for linux and windows seems unconventional #1
Comments
Referencing the original PR: tauri-apps/tauri#2736 this was done to mirror the behavior of electrons setAppLogsPath function. The reason for this is that most packaging formats (snap, appimage, flatpack) reserve an Application Directory for you, that in many cases is the only folder that is writable by default. So this really boils down to sandbox restrictions and we don't want peoples logging to fail because of missing sanbox privileges. If you never plan on distributing snap, appimage or flatpack formats and only ever ship deb packages, or you manually request the necessary sandbox privilegess than you can use |
While following setAppLogsPath is fine by me, i too feel like the config dir is "wrong", on linux and windows btw. On the other hand i'm not a fan of splitting up app files into multiple dirs, but that's just personal preference i guess. |
On Linux either Can someone link to upstream info/issues on sandboxing? If they don't support something as simple as proper place for logs instead of config directory, then we should create corresponding tickets for them to add such support. |
feat: Add example with an `emit_all` event
/upstream tauri-apps/tauri |
I believe the convention for storing the log files on Linux is, using the path
/var/log
.Is there a specific reason for choosing
.config
instead? (https://github.com/tauri-apps/tauri-plugin-log/blob/dev/src/lib.rs#L106)The text was updated successfully, but these errors were encountered: