Hi everyone, I have been getting back into photography lately and switched to using linux full time about a year ago.
I ended up deciding to use digikam as my photo library management tool and then edit in darktable. both applications I decided to use the appimage for easier use and to have the necessary dependencies to get things like opencl to work, (I had a hard time getting it to work with the .deb)
now I also use multiple machines and recently learned that you can create .home and .config folders for each appimage to have all their settings etc save there, and it seems that this would make it pretty portable.
would it be a bad idea to for example keep the appimages and their folders in a synchronized folder like with nextcloud to use the same* appimage across machines. I never have the same machine on at a time but it would be nice to have all the settings sync’d but im not sure it would then break something since two machines use nvidia gpus and the other uses an amd gpu
Appimage is an immutable exe. Like a CD ISO It stores config in a home folder variable location.
oh to bad. I thought it was more akin to an apple program.
macOS applications are folders and that will never stop being weird to me. They basically use the same setup as windows but instead of making the application the executable in the folder they turn the whole folder into the executable
thats what makes them so portable. im not sure about nowadays but you could just move the app to another machine and you where all set.
I wonder how that works on multi-user systems. How do they structure that so that settings are per-user?
Im not sure. I do know I have had to go into the image and change files in the tree before but I don’t really remember why.
Oh, you’re thinking of applmages
yeah thats what this is about. appimage portability.
No. App_l_mages.