Support for .py python script files in Mergin projects

[holesond]

As far as I know, uploading python script files (and bash scripts) to Mergin projects is not allowed since pull request #370. However, some of our projects stored on a self-hosted Mergin server (Community Edition) need to distribute python or bash scripts together with QGIS projects. The scripts help project users to automatically create new vector or raster layers on demand or process data already supplied by the users. The scripts are often tightly integrated with the projects so distributing and updating them via a different channel such as GitHub instead of Mergin would be inconvenient.

Would it be possible to add a per-project or a server-wide configuration option which would disable the "dangerous file type upload restriction"?

[MarcelGeo]

Hey @holesond . Yes we can probably introduce some global env option to disable this behaviour. You can probably store this files in zip files.

[holesond]

@MarcelGeo A global env option to disable the file type upload restriction would be good enough for us.

I think that storing .py, .bat or .sh files in zip archives would not be very convenient as each user would need to unzip them each time they are updated on the server. I think the users would also need to delete the unzipped .py files before each project sync. This may not always be easy especially when there are several .py/.bat/.sh files stored in different folders of a project. I think that it would effectively require running another script before and after each sync to perform this work automatically, which would be unnecessarily complicated.

[MarcelGeo]

Ok, we can take a look at this. @tomasMizera .. for custom deployments this could be fine to add some allowed extensions as env variable.