Calibre Web VS Portainer

Calibre-web can, I use it with an app on an iPad. It’s not immediately obvious how to access it, but here’s a GitHub issue with good info: https://github.com/janeczku/calibre-web/issues/2103

You can simply use this website to send yourself books using the web browser on the kobo

https://send.djazz.se/

Or you can host your own "Kobo store" using calibre web and use that to sync your books

https://github.com/janeczku/calibre-web/wiki/Kobo-Integratio...

There are already some very good ebooks solutions out there so there's really no need. Calibre for the backend and database management, Calibre-Web for the front end, and Openbooks for content.

I have a carefully-curated calibre-web library that is 100% epubs. I have a kindle to which I usually send books from calibre-web with the 'send to e-reader' button, and it works great.

Worthy of note the Calibre-Web[0] project, which builds atop Calibre library to provide powerful web interface. The project and its maintainer deserve some love and support.

[0] https://github.com/janeczku/calibre-web

Calibre Web: https://github.com/janeczku/calibre-web

Calibre-web

A pihole, of course. A backup script runner. An eink dashboard.. A book server.

We see that both of our containers are working and no restarting issues. So all looks good at first glance. Now we can move to the next step. We could now deploy NTFY container, but I would like to deploy a Portainer. Why?

It's crucial to have an effective access management system that allows you to robustly manage user identities and permissions across your clusters. Although Kubernetes includes an advanced RBAC implementation, this only works within a single cluster. A dedicated Kubernetes management platform such as Rancher or Portainer is required to cohesively configure identities and grant users the multi-cluster access they require.

Check it out https://www.portainer.io/

Portainer is a container management platform that provides a powerful web interface to administer your workloads. It natively supports Kubernetes environments to help you manage your Pods, Deployments, Helm charts, and other cluster resources. Portainer also provides robust RBAC capabilities and an external authentication layer, letting you grant team members access to Kubernetes through Portainer without directly exposing your cluster.

This episode is actually why I started this series in the first place. I am an active Docker user and Docker fan, but I like containers and DevOps topics in general. I am a moderator on the official Docker forums and I see that people often struggle with the installation process of Docker CE or Docker Desktop. Docker Desktop starts a virtual machine, and the GUI is to manage the Docker CE inside the virtual machine even on Linux. Even though I prefer not to use a GUI for creating containers, I admit it can be useful in some situations, but you always need to be ready to use the command line where all the commands are available. In this episode I will use Ansible to install Docker CE in the previously created virtual machine, and I will also install a web-based graphical interface, Portainer.

Portainer

> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?

From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.

You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.

So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).

That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)

In this section, we will add Portainer to help us in managing our Docker containers. You can find more details about it here. To integrate Portainer into our EC2 project, we can follow these steps:

Git issues pointing to: https://docs.portainer.io/v/ce-2.9/start/install/agent/swarm/linux gives a ERR_TOO_MANY_REDIRECTS.