Personal Best Practices #2572
Unanswered
messengerstinxx
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Until a new Casa)Srelease comes out, I always do the following (just to maintain a tolerable user experience)
(1) Install the latest Docker Engine (since the CasaOS Docker Engine is extremely outdated)
This ensures that the maintainers packaging remains up to date
➭ REF. VIDEO: https://www.youtube.com/watch?v=mN8DC54UtM8
➭ REF. DOCS: https://docs.docker.com/engine/install/debian/
(2) Install CasaOS
This gives the familiar UI an updated foundation to work on since the installer script will only install components that are already missing, however it also leaves the Docker install in-tact.
➭ REF.URL: https://casaos.zimaspace.com/
(3) Add your preferred custom App Stores
As this brings more apps into your CasaOS install
➭ REF.URL: https://awesome.casaos.io/content/3rd-party-app-stores/list.html
(4) For Custom Installations
Although there are multiple alternatives for GUI based Docker Management I always install Portainer via the CasaOS App Store as my first Docker Container. As doing so now allows...
» Portainer is a GUI alternative to the classic CLI "docker-compose up -d" *.yml scripting
» A more granular experience with custom Containers and Stacks
» Portainer's Stacks builder is editable, thus eliminating the need to re-pull images and you can change your build scripts on the fly
» Docker Container features such as creating MAC VLAN's is possible when building in Portainer
» Portainer allows a comprehensive Docker Container troubleshooting and Administration alternative compared to that of CasaOS
(5) Many Custom Installations are also Importable
Depending on the complexities of your Portainer build, there's often a good chance that whatever new apps that now appear in the CasaOS Legacy App (To Be Rebuilt) homescreen window can now be Imported into CasaOS after following a few on-screen prompts.
Some imports may fail if they're part of Container Stacks, or have unique customizations that are unrecognizable within the CasaOS application builder (such as MAC VLAN's).
IF that process fails, and yet you still prefer to have all installed apps working as intended within the CaasOS applet, simply stop and delete the Portainer Container App and rebuild it in CasaOS's Customized App Menu.
Perhaps if the next iteration will ever be released, it could focus on keeping the App Store and File Manager features... but now integrate a preferred App Builder Administration Tool function such as Portainer, Dockge or Code Server, and replace the familiar Desktop UI with a Homepage Tool similar to that of Homarr, Homepage or Dashy.
... basically make the next release of CasaOS a buildable all in one app of combining your choice of Docker Management Tools... The Familiar App Store and File Manager and a preferred Homescreen App into an all in one App experience.
All reactions