this post was submitted on 20 Aug 2023
36 points (87.5% liked)

Selfhosted

40219 readers
986 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
36
grocy bangs head (poptalk.scrubbles.tech)
submitted 1 year ago by pootriarch@poptalk.scrubbles.tech to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

i've tried grocy a few times over and it's burned a lot of time and brain cells. is there anything that does this (or even much less than this) and just works?

i understand why it was made this complex - i code and i work with people who want everything to be so theoretically 'flexible' that nothing simple works, so i'm used to the abstraction layers. but

  • first try: looked at number and size of packages, no tree-shaking, code doesn't pass sniff test. dozens of megabyes for this? nope
  • second try: well i don't want to build this myself. i'll put it in its own instance to minimize security exposure. but hey, this release is months old and these terrible bugs have been fixed, i'll just grab newer code. missed the thing where database migrations are tested only from official releases. database breaks.
  • i learn sqlite syntax and reconstruct the database.
  • months later i download new grocy android client, which expects a v4 grocy back end. all recipes break.
  • i download official grocy v4 release (the third one in rapid succession, due to major bugs - luckily i hadn't tried too early).
  • database breaks.

i'm done. i don't care that i lose the work i already put into it. i just want to open the cupboard twice and have the same thing be there both times. help

you are viewing a single comment's thread
view the rest of the comments
[–] pootriarch@poptalk.scrubbles.tech 0 points 1 year ago

i haven't tried the docker route - it seems fairly new. it also doesn't seem like it would fix the issues i ran into. containerization is great for insulating the app from external dependency hell and environmental variation. but the problems i've had involve its own code and logic, and corruption of a sqlite database within its own filesystem; wrapping issues like that in a docker container only makes them harder to solve