Grocy - ERP Beyond your fridge
-
@yusf It also has a recipe function which is kind of neat. It will tell you what you can make based on your inventory. I could see some people just using this for inventory and some for just recipes. Reference: https://en.demo.grocy.info/recipes
-
@yusf said in Grocy - ERP Beyond your fridge:
I can see a benefit for using it in small-scale industrial kitchens or perhaps in community kitchens but other than that, ¯_(ツ)_/¯
From the website:
Waste less!
Except time that is
Mmm, as far as I can see Cloudron can absolutely address TWO clients categories, which are BUSINESSES and FAMILIES, think about it so that app would just be fantastic to add for that utility, and that said even for business for lists of supply needs etc. ...
Andy -
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 ...)
-
@girish I'd guess this is it:
https://github.com/grocy/grocy/pull/1380 -
What an awesome app!
-
I sorta skimmed past this before, but I think I have a usecase for this.
-
How do you get this to work in a LAMP app?
what I did was...
- extracted the zip file inside the public folder of a new LAMP app
- changed the permissions of everything to www-data (Cloudron)
I got a no permission to access this page (or something of that sort). Then, I..
- moved all content to the "home" directory of the LAMP app
- moved the contents of the "public" folder that was in the zip file to the "public" folder of the LAMP app.
Unable to run grocy: /vendor/autoload.php not found. Have you run Composer?
P.S. I'm trying to use a subdomain (xx.mydomain.com) and not the root domain if that makes any difference.
-
@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?
-
@andreasdueren Did you fix that in the meantime? (Sorry for not reacting )
-
@RoboMod
that half-fixed things.(100% fixed, see below for details)What I did was move all folders/files to the home folder and moved the content of the "public" folder (the one that's in the Grocy zip) to the LAMP's public folder. I'm going to check the config.php in the /data folder for path issues. Did you disable (NGINX) url rewriting?
Edit: Actually, your solution @RoboMod fixed the issue. I forgot I had edited the config.php base url and once reverted back to its defaults. the login page loaded and it's all working as expected. Thank you!
// When running grocy in a subdirectory, this should be set to the relative path, otherwise empty // It needs to be set to the part (of the URL) AFTER the document root, // if URL rewriting is disabled, including index.php // Example with URL Rewriting support: // Root URL = https://example.com/grocy // => BASE_PATH = /grocy // Example without URL Rewriting support: // Root URL = https://example.com/grocy/public/index.php/ // => BASE_PATH = /grocy/public/index.php Setting('BASE_PATH', ''); // The base URL of your installation, // should be just "/" when running directly under the root of a (sub)domain // or for example "https://example.com/grocy" when using a subdirectory Setting('BASE_URL', '/');
Things to note for future reference:
- all files/folders go into the LAMP's home directory.
- copy over and rename config-dist.php into /data/config.php and tweak the settings like "week starts on Monday" but no need to edit the base path/url if using the domain's root or a subdomain.
- disable phpmyadmin per the doc instructions here