You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing all different branches: 1.0, 1.1 and 2.0. Only 1.0 is updated to alpine 3.11, the other aren't. Also only the master branch includes compose files.
What's actually the difference between these branches and shoulnd't they all be updates in the same manner?
The text was updated successfully, but these errors were encountered:
Wow! Somehow missed this until just now. Apologies for that!
The reasoning you're seeing the different branches and lack of consistency is because, honestly, the repo has been a mess! 😆 It started off as a single project showing cats, but then I wanted different versions to demonstrate rolling updates. So, I started with branches. But, then the issue was that I wanted to keep all of the versions updated, so I actually went back to only the main branch with sub-directories for the individual versions. Yes... it deviates from the standard development workflows (as I'm backpatching old versions), so the repo is kinda messy. I'm trying to figure out how to balance the original need (multiple versions to demonstrate updates), yet also still keep each of those versions updated too.
I'm also wanting to add GitHub Actions to it, so have to fit that into the balance so it's still easy for someone else to follow. Maybe I just need to clean it up and have only a single version of the app going now 😆
Hello, thank you for this great repo.
I'm seeing all different branches: 1.0, 1.1 and 2.0. Only 1.0 is updated to alpine 3.11, the other aren't. Also only the master branch includes compose files.
What's actually the difference between these branches and shoulnd't they all be updates in the same manner?
The text was updated successfully, but these errors were encountered: