Electric Eel no longer uses ix-applications for apps data storage, moving it instead to /mnt/.ix-apps. That’s where changes to apps are reflected in 24.10
Data from previous app installs retained in the legacy ix-applications can be used to migrate or recreate applications in 24.10, but I’d say that once you have everything back up and running you should be able to safely delete the unused ix-applications dataset.
Do you mean like shell access to check for configuration changes? ls -a /mnt or ls /mnt/.ix-apps will let you view it.
Documentation for a new major version is updated alongside development changes. You can use the Product and Version selector at the top of the page to select a specific stable or early release version.
Thank you, it seems data is being left on ls /mnt/.ix-apps/app_mounts as nginx-proxy-manager has been uninstalled yet application data still exists. The data has been deleted. I don’t know if this is by design. Maybe the user should have the option they want to keep or delete that data during uninstall.
In this case I need to delete the following data in order to have a clean install of that particular app. rm -drf /mnt/.ix-apps/app_mounts/nginx-proxy-manager
Unfortunately the administrator account does not have privileges to delete such data. cannot remove '/mnt/.ix-apps/app_mounts/nginx-proxy-manager/data/database.sqlite': Permission denied
What’s the official way to remove data from the data set? root?
Thank you for clarifying that this is a work in progress. A simple solution. Allow the user to check a box during uninstall whether or not to delete the app data volume.
Keep in mind both in documentation and implementation that a user may need to rescue data from app_mounts/some-app manually. It could be kept read only, but should be made accessible.
Why are we still using ix systems datasets for app data and not just allowing a host path to be set for everything? Not sure why we are splitting data into 3 different places and not just doing it normally like we have been on linux forever?
You can still do that, but if you provide a host path, its permissions need to be set up the way the target app expects them to. I had issues with setting up host dirs for Home Assistant since PostgreSQL could not init its database files with a directory owned by apps:apps.
Other than that, the dirs are actually separate ZFS datasets, not just directories in /mnt/.ix-apps. They’re also hidden from the web UI, which is weird… They can be listed with mount | grep /mnt/.ix-apps/app_mounts + /usr/sbin/zfs list and deleted with umount /etc/.ix-apps/app_mounts/<path to each mount> + /usr/sbin/zfs destroy pool-name/ix-apps/app_mounts/app-name.
I created a separate dataset for apps and gave Modify permissions for apps:apps. When installing apps, I create the necessary folders and specify Host Path instead of ixVolume. This way I have full control over the files the apps uses