• 3 Posts
  • 103 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle

  • Portainer is a container management system. It’s purpose is to allow you to manage containers in an easy to use GUI.

    ZaneOps is a PaaS that allows you to automatically build and deploy web apps into containers without having to configure the underlying infrastructure at all.

    For example, to deploy my static site on Portainer, I’d have to build my static site, containerize it, upload the container image to a registry (or directly to Portainer), then use Portainer to configure the environment and deploy the container. Then I’d have to configure a reverse proxy or web server to serve the contents of the container. If I wanted to continue working on that static site I’d need to configure some kind of CI/CD pipeline to try and automate all that previous work.

    With ZaneOps, I store the Astro/11ty/other SSG files in a Git repo, and on any commit ZaneOps will automatically recognize the SSG framework I’m using, use Docker Swarm to spin up a container to build the site into static files, containerize the resulting files for me, and deploy the container. It then uses Caddy underneath to serve what’s in the container including provisioning SSL certs for the site. It will health check the new container before deploying it in a blue/green deployment model so that the old site is removed only after the new one is up and available. It’s the same workflow as deploying a site to GitHub Pages using GitHub Actions if you’ve ever done that.

    Ultimately. You end up with the same result, a containerized workload, but ZaneOps takes your GitHub Repo and turns it into a built, running, containerized workload automatically. Automating the deployment of my own web apps using Portainer would be at the very least clunky and require a lot of surrounding infrastructure. It’s not something Portainer just does out of the box.

    Cockpit isn’t much like either, it’s just a web based server management tool.














  • I’m just using the app. I think it’s the nicest, most functional, and best looking music app outside of PlexAmp… however I absolutely agree with you that I really really wish it was just its own app… you can make this easier on yourself by editing the quick bar at the bottom of the app. When I open the Emby app it’s one tap to get to the music and then at least I don’t have to “dig through” it to get there.

    I have an AppleTV4k Hooked up to my tv and 5.1 sound system so I can Airplay to that with my iPhone. Same goes for my HomePod in the kitchen when I’m cooking. If you’re not on iOS you can also cast to any device with an Emby app but there is less flexibility there.

    I am in the same boat as you in that I’d love a dedicated app, I’m just waiting for one to come along that doesn’t suck. The FinAmp project had gotten me excited since it was ostensibly Jellyfin’s take on PlexAmp but it looks god awful and the functionality isn’t there. They have a beta version that’s a complete redesign but it also sucks terribly in my opinion.

    Since you mentioned podcasts, AudioBookShelf as a back end with the “ShelfPlayer” app on iOS has been phenomenal. The ShelfPlayer app even works with my Oauth connection which is so awesome. Wish Emby or Jellyfin did that lol.




  • Half of the equation is that those making the PWA need to make it well. The other half is that the platform you install it on has to support it well. And Google and Apple have decided to support PWAs as little as possible (in some cases removing support for them altogether. See Apple removing the ability to use them entirely in the EU). And since those two companies make the two most commonly used mobile OS’… well it’s better to just go with a native app.

    The #1 biggest problem with PWAs on iOS for example is the lack of push notification support, which for a lot of apps is a nonstarter. Is that the PWA makers fault? No. Does it make that PWA suck anyway? Yes.