Here is some update: the mobile app now supports the newest Grocy server version. I tried to get it using the Cloudron Ldap. This doesn't work out of the box but there is a patch waiting to be merged. I applied and tweaked it and can authentication as Cloudron user now.
(I'm thinking about packaging Grocy for Cloudron but might need some help on that 
...)
Here it is: https://git.cloudron.io/RoboMod/minio-auto-deleter. If there are any questions, don't hesitate to ask!
I just installed it in a LAMP App. Works great.
The next major release brings LDAP support. I'll try to upgrade soon after next release of the Android app.
Hi Cloudron Team,
thank you for the great feature of letting people now about apps going down via E-mail. It now happened multiple times that this was just a temporary problem and the app was already back online when I checked my mails. So, it would be nice to have a "App XXX is up" or similar E-mail telling me that I don't have to take any action.
Best
RoboMod
@girish @jdaviescoates Yes, it is. But its still not fully compatible to Cloudron. I'll create a patch from my changes, soon.
Hey there, are there any plans to introduce some sort of distribution into Cloudron? I'm thinking of deploying apps to different machines controlled via one interface.
@ApplegateR But that was the version creating the backup. And the docs clearly say that it is required to use the identical version to restore a backup.
@lucidfox It works. But the next major release of Grocy breaks the API so the Android client has to catch up these changes.
Good news: I was able to get one step further! I modified the restore.js (changed "$scope.configureBackup.backupFolder" to "$scope.backupFolder") and now the restore process seems to be running.
@girish That works great! Many many thanks for you prompt support!
@girish Yes, exactly. I think the necessary modules would be:
LoadModule ldap_module /path/to/mod_ldap.so
LoadModule authnz_ldap_module /path/to/mod_authnz_ldap.so
But I'm not 100% sure
@girish Wuhu! Thats nice. Would you be willing to activate it in the next release or so? (I'm not sure which modules it would require exactly. But I could search them.)
Hi there. I would like to use a .htaccess Protection in combination with the Cloudron LDAP. If I didn't miss it, the necessary modules are not loaded by the Apache config of the LAMP app. Would it be possible to active them?
Best
RoboMod
@andreasdueren Did you fix that in the meantime? (Sorry for not reacting 
)
@humptydumpty Sound like a path issue. All the folders and files for Grocy are in the "home" folder of the LAMP app. Hence, the "vendor" folder is also in the "home" folder so that the "app.php" can successfully load the path "/vendor/autoload.php". Does that help?
+1
There is already a Docker packaged version mentioned on that page.
Good news: I was able to get one step further! I modified the restore.js (changed "$scope.configureBackup.backupFolder" to "$scope.backupFolder") and now the restore process seems to be running.
@girish Reloading brings me back to the restore page. But I discover something else: watching the browsers consol there came up some errors:
angular.js:13920 TypeError: Cannot read properties of undefined (reading 'backupFolder')
at $scope.restore (restore.js? [sm]:290:1)
at fn (eval at compile (angular.js:14817:15), <anonymous>:4:212)
at b (angular.js:15906:18)
at e (angular.js:25885:17)
at b.$eval (angular.js:17682:16)
at b.$apply (angular.js:17782:20)
at HTMLFormElement.<anonymous> (angular.js:25890:17)
at HTMLFormElement.dispatch (jquery.min.js:3:8066)
at r.handle (jquery.min.js:3:4767)
(anonymous) @ angular.js:13920
DevTools failed to load source map: Could not load content for https://my.xeac.de/3rdparty
/js/showdown.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://my.xeac.de/3rdparty/js/angular-cookies.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
Error: $scope.configureBackup is undefined
$scope.restore@https://my.xeac.de/js/restore.js:290:13
fn@https://my.xeac.de/3rdparty/js/angular.min.js line 233 > Function:4:212
b@https://my.xeac.de/3rdparty/js/angular.min.js:126:128
e@https://my.xeac.de/3rdparty/js/angular.min.js:276:196
$eval@https://my.xeac.de/3rdparty/js/angular.min.js:145:347
$apply@https://my.xeac.de/3rdparty/js/angular.min.js:146:52
Lc[b]</compile/</<@https://my.xeac.de/3rdparty/js/angular.min.js:276:247
dispatch@https://my.xeac.de/3rdparty/js/jquery.min.js:3:8066
add/r.handle@https://my.xeac.de/3rdparty/js/jquery.min.js:3:4767
angular.js:13920:17
From what I see here, I would guess the code behind does not fit the frontend. Any hint on how to solve this?
@ApplegateR But that was the version creating the backup. And the docs clearly say that it is required to use the identical version to restore a backup.