I’m looking for testers for a closed Google Play test of a shopping list app for Home Assistant.

The app connects directly to your Home Assistant instance and is aimed at making shared shopping lists simpler and faster to use on mobile.

Current features:

• Connects to your Home Assistant instance
• Displays and manages your shopping list
• Add, check, sort, rename and remove items quickly
• Access to all lists configurated in your HA instance
• Automatic sync with Home Assistant
• Offline caching

If you’d like to join the test, please send me your Google Play email address via private message. I’ll then send you the opt-in link.

Edit: Testers just need to install the app and keep it on their phones for 14 days. (Really, that's all that google asks for....). Only after that I'm allowed to publish it.

Edit2: It's also available on github: https://github.com/robNice/HA-ShopList

Just don't install the playstore-apk, as that version lacks the in app updates via github.

Testers I found so far: 3/12

@[email protected] Den offensichtlichsten Kandidaten hast du extra für mich übrig gelassen. Merci ;)

Es tut mir leid.

I'm quite a noob, when it comes to actually work with github, though I used to work with git to version my work since quite a while. So my approach / plan could be totally wrong.

I hope anybody out there could help me, give me the right idea.

What I have:

My Project is hosted on a self hosted forgejo instance on my lan. I have two branches, dev and main. Everytime I push to dev, a forgejo workflow I wrote builds a fresh docker-image and restarts the container. I can test the new Image right away, which is quite neat.

The project has reached a point, where

a) I'm not embarrassed anymore about my code

b) I think, this could be a nice docker image for others

c) I also think it would be cool if maybe others would contribute

Enter Github

I set up mirroring forgejo to github. But since my dev branch has my forgejo workflows workflow file (containing some details about my local server infrastructure) I decided to only mirror the main branch, which has that workflow excluded from the repo.

I also set up a github workflow (action) where, when my commit to main was properly tagged, it will create and register a 'latest'-tagged docker-image for the public.

This can all be done just by using my IDE and has a low manual workflow footprint. (Develop on dev, push, test on local server. When happy, checkout main, merge dev to main, push: image is live)

This all works great.

The only flaw in all of this is, that, even if I'd allow to do PRs from the public main branch on github, forgejo would never see that, means: Nobody may be able to contribute.

I'm at the point, where I think, maybe my whole concept is wrong.

How could I set all this stuff up, to:

• still build local images
• still build public images
• allow github users to do PRs

all of that without building something that requires a tedious amount of manual workflow steps.

Du musst besoffen bestellen!

Recipe taken from the official Italian Kitchen Academy:

https://www.accademiaitalianadellacucina.it/sites/default/files/Rag%C3%B9%20alla%20bolognese%20-%20updated%20recipe_20%20April%202023.pdf

EDIT: Tja, verhamlosen wollte ich ihn nicht. Bild aktualisiert ;)

Ein von mir sehr sehr geschätzter Künstler und irgendwie auch sehr unbekannt. (Auch wenn ihr was gegen Deutschrap haben solltet: unbedingt reinhören!)