szurubooru VS Portainer

I've been accumulating art and pictures downloaded from the internet, what's a good way to store and tag them with the original artist and source? Maybe a simple solution would be just adding appropriate EXIF data to the files? This approach would still require a good folder structure to make sense of. Another option I came across was https://hydrusnetwork.github.io/hydrus/index.html, but after trying it, the experience was really janky and not pleasant. Or I could even host an image booru so the collection would benefit others too, with https://github.com/rr-/szurubooru perhaps?

How do other people deal with it, I'm curious to hear.

also agree with hydrus network. im at 18million items. next best thing is probably something like a selfhosted booru server so that you can remotely organize files during your downtime on the toilet or jury duty.

I'm your savior, together with https://github.com/rr-/szurubooru

There is also https://github.com/rr-/szurubooru/discussions

On unraid postgres is used by szurubooru, mealie, and grafana. I don't know specifically what but I know redis is also used by one of the apps in the cloud group as well.

name: mybooruname #yes this next line is empty as i mention above, but the [INSTALL.md](https://github.com/rr-/szurubooru/blob/master/doc/INSTALL.md) says you can skip lines of which you want to use the defaults. or should i add something here? domain: secret: mysecretstring delete_source_files: no thumbnails: avatar_width: 300 avatar_height: 300 post_width: 300 post_height: 300 user_agent: max_dl_filesize: 25.0E+6 convert: gif: to_webm: false to_mp4: false allow_broken_uploads: false smtp: host: localhost port: 25 user: myusername pass: thisisapass from: noreply@localhost enable_safety: yes # the rest is just regexes for tags, pools, usernames, and passwords, and user rank privilege stuff

If you need tagging / users and stuff for the images, I’ve used https://github.com/rr-/szurubooru

Honestly, your project makes me want to contribute to I but I have absolutely no experience with Golang. I see a lot of potential in it and because it's comparatively new and barebones, there aren't any entrenched concepts like with more mature projects. Like, if you ever get around to implementing a more comprehensive organization system, do check out Szurubooru. Tags and tag categories can replace Albums, Faces, Places, Objects, Themes, Colors, EXIF data and so much more. You can still use tooling like AI recognition, geotagging, EXIF readers, and whatnot to populate them accordingly but being standardized as TAGS makes searching and crawling much easier. Not to mention defining custom tags would allow for a very versatile usage. And with a fluid browsing like yours, it will be a dream app.

I can share something like that. There is this imageboard called (Szurubooru)[https://github.com/rr-/szurubooru]. People use such boards to host their anime and hentai stuff.

I kinda have something for Twitter accounts, said thing being this extension, but I stupidly don't use it enough. You see, I archive my posts using szurubooru, which is on a by-post basis, so everything has to be added one by one. (Technically, you can upload multiple at once but there's no function to add tags before upload, only after.)

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.

I am currently running Portainer, but webhooks (GitOps) appear to be broken ( [2.19.0] GitOps Updates not automatically polling from git · Issue #10309 · portainer/portainer · GitHub ) and so I cannot send webhook to redeploy a stack. So, looking for alternatives. Using this as a good excuse to learn more about docker and CI/CD etc.

A Synology NAS running Portainer (https://www.portainer.io/) running Paperless NGX (https://github.com/paperless-ngx/paperless-ngx)

This works better than I can possibly tell you.

I have an Epson WorkForce ES-580W that I bought when my mother passed away to bulk scan documents and it scans everything, double-sided if required, multi-page PDFs if required, at very high speed and uploads everything to OneDrive, at which point I drag and drop everything into Paperless.

I could, thinking about it, have the scanner email stuff to Paperless. Might investigate that today.

Paperless will OCR it and make it all searchable. This setup is amazing, I love living in the future.

> I've come to the conclusion (after trying kops, kubespray, kubeadm, kubeone, GKE, EKS) that if you're looking for < 100 node cluster, docker swarm should suffice. Easier to setup, maintain and upgrade.

Personally, I'd also consider throwing Portainer in there, which gives you both a nice way to interact with the cluster, as well as things like webhooks: https://www.portainer.io/

With something like Apache, Nginx, Caddy or something else acting as your "ingress" (taking care of TLS, reverse proxy, headers, rate limits, sometimes mTLS etc.) it's a surprisingly simple setup, at least for simple architectures.

casaos it just makes things like backups, offsite syncing and many other nas related things so much easier to manage. And gives you a proper nas like experience similar to that in which you'd fine on companies like tnas or synology. I actually also use it as a replacement for portainer when i don't need the more advanced features it offers

> I moved to docker swarm and love it. It's so much easier, straight forward, automatic ingress network and failover were all working out of the box. I'll stay with swarm for now.

I've had decent luck in the past with the K3s distribution, which is a bit cut down Kubernetes: https://k3s.io/

It also integrates nicely with Portainer (aside from occasional Traefik ingress weirdness sometimes), which I already use for Swarm and would suggest to anyone that wants a nice web based UI: https://www.portainer.io/

Others might also mention K0s, MicroK8s or others - there's lots of options there. But even so, I still run Docker Swarm for most of my private stuff as well and it's a breeze.

For my needs, it has just the right amount of abstractions: stacks with services that use networks and can have some storage in the form of volumes or bind mounts. Configuration in the form of environment variables and/or mounted files (or secrets), some deployment constraints and dependencies sometimes, some health checks and restart policies, as well as resource limits.

If I need a mail server, then I just have a container that binds to the ports (even low port numbers) that I need and configure it. If I need a web server, then I can just run Apache/Nginx/Caddy and use more or less 1:1 configuration files that I'd use when setting up either outside of containers, but with the added benefit of being able to refer to other apps by their service names (or aliases, if they have underscores in the names, which sometimes isn't liked).

At a certain scale, it's dead simple to use - no need for PVs and PVCs, no need for Ingress and Service abstractions, or lots and lots of templating that Helm charts would have (although those are nice in other ways).