Hey @wassimj,
i think there is no technical blocker to do this even without manager. The above mentioned manual account solution works for the blender connector or for plain python scripts using specklepy.
As for installing the blender connector on linux + blender as flatpak here’s how i’ve got it working:
- find the version number of python that is used by the current blender install, for Blender 3.0 its Python 3.9.7
- create a new virtual env with a matchin python version, and install the requirements of bpy_speckle into that env
- get the user specific folder for the type of installation that was used, for Flatpak its in: ~/.var/app/org.blender.Blender
- to install the speckle addon copy ( or symlink ):
- the bpy-speckle folder to the addons folder, so that this exists: ${blender_user_config_dir}/config/blender/${blender_version}/scripts/addons/bpy_speckle
- the site-packages directory of the bpy_speckle dependecies under the name modules so that the ${blender_user_config_dir}/config/blender/${blender_version}/scripts/addons/modules directory exists, and its content is the dependencies of bpy_speckle
- symlink the ~/.local/Speckle folder into ${blender_user_config_dir}/data/ so that the ${blender_user_config_dir}/data/Speckle folder exists. This way the machine wide accounts and objects cache is used even in a sandbox installed blender
the steps might wary depending on ur distro / installation mechanism, but the general direction of the steps are the same.
If you need help with setting it up, let me know, at some point we might like to officially support this too.