tauri icon indicating copy to clipboard operation
tauri copied to clipboard

feat(core): allow config app dir override

Open Legend-Master opened this issue 2 weeks ago • 5 comments

Reference: https://github.com/tauri-apps/tauri/issues/3109

Closes https://github.com/tauri-apps/plugins-workspace/issues/3020 We could still do https://github.com/tauri-apps/plugins-workspace/pull/3022 by changing filename to take a path (which can be relative)

Legend-Master avatar Dec 07 '25 09:12 Legend-Master

Package Changes Through a08aa1e45ab78a81e2c2229778bc0e7c2bc5a5aa

There are 3 changes which include tauri with minor, tauri-macos-sign with patch, tauri-bundler with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
tauri-macos-sign 2.3.1 2.3.2
tauri-bundler 2.7.4 2.7.5
tauri 2.9.4 2.10.0
@tauri-apps/cli 2.9.5 2.9.6
tauri-cli 2.9.5 2.9.6

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

github-actions[bot] avatar Dec 07 '25 09:12 github-actions[bot]

This either needs to be windows only or have more warnings. Once you package the app on Linux and macOS most paths won't work anymore while on Windows they'd still work (on perUser installs).

Speaking about paths, would it make sense to still resolve the $DESKTOP etc variables (except the APP ones of course) ?

For Linux another one like $APPIMAGE or simply resolving the path relative to the APPIMAGE env var instead of current_exe would help as well since appimages are in lines with the portable app idea here, the current_exe is just a temp read-only path

FabianLars avatar Dec 07 '25 10:12 FabianLars

Once you package the app on Linux and macOS most paths won't work anymore while on Windows they'd still work (on perUser installs).

So my original idea was to only use this in non-packaged environment like portable apps and during debugging (in target directory), but I wasn't sure what name to use here and just went with this, we could expand the documentations of course

Speaking about paths, would it make sense to still resolve the $DESKTOP etc variables (except the APP ones of course) ?

Most of the paths still need to work I think, people might want to access those directories not just for storing their own data?

For Linux another one like $APPIMAGE or simply resolving the path relative to the APPIMAGE env var instead of current_exe would help as well since appimages are in lines with the portable app idea here, the current_exe is just a temp read-only path

Nice call, I'll change it to use current_binary here instead

Legend-Master avatar Dec 07 '25 11:12 Legend-Master

Most of the paths still need to work I think, people might want to access those directories not just for storing their own data?

I meant in the new path config, so you could say your override should be somewhere on the Desktop or in the Documents dir.

Nice call, I'll change it to use current_binary here instead

totally forgot that's a thing x)

FabianLars avatar Dec 07 '25 11:12 FabianLars

I meant in the new path config, so you could say your override should be somewhere on the Desktop or in the Documents dir.

Ah I see what you mean now, good idea I guess

Legend-Master avatar Dec 07 '25 12:12 Legend-Master