plotman VS Portainer

Yes, see https://github.com/madMAx43v3r/chia-plotter for plotting with a ramdisk and https://github.com/ericaltendorf/plotman to automate everything.

Plotman is what you want. You can plot on multiple drives (tmp), then cache the completed plots on destination drives/directories (dst). Then the archive function can rsync them to an array of archive drives. Very easy to modify the config .yaml file then run "plotman plot" and "plotman archive". https://github.com/ericaltendorf/plotman

Plotman: v0.5.1

Yeah. Plotman config guide shows you how to set it up for madmax. Its as easy as changing the "type" variable in the config file from "chia" to "madmax" and then changing your other plotting variables to what they should be be for madmax.

Madmax plotter, Swar plot manager, and Plotman plot manager all support portable plots for pools now. Others probably do, but I'm not as familiar with them. Update to the latest versions for the best results, and double-check your configuration files as some settings may have changed since your last update. And you can also use plot managers with Madmax these days, if you want to take advantage of workflow management (multiple destination drives, parallel plotting on bigger plotters, less scrolly logs, etc).

The v0.5 plotman includes support for madmax plotting as well as chia pool plotting. If you're feeling brave, update your plotman with: pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@main

from the default config:

# upgrading chia to the latest version cd chia-blockchain/ . ./activate chia stop -d all deactivate git fetch git checkout latest git reset --hard FETCH_HEAD git status sh install.sh . ./activate chia init edit file: nano /home/YOURUSERNAMEHERE/chia-blockchain/setup.py change the chiapos==1.0.2 to chiapos # resolving all config problems sudo apt install aptitude sudo aptitude -f install build-essential aptitude install cmake sudo aptitude install cmake (first type n, then type y) sudo aptitude install python3-dev (first type n, then type y) cd git clone --branch combined https://github.com/pechy/chiapos.git cd chiapos mkdir -p build && cd build # configuring flags to compile CFLAGS="-mtune=native -march=native" CXXFLAGS="-mtune=native -march=native" cmake ../ 1241 cmake --build . -- -j 6 # compiling cmake --build . -- -j 6 . ~/chia-blockchain/activate cd ~/chiapos && python setup.py install # finding all old chiapos files to replace find / -name chiapos.cpython-38-x86_64-linux-gnu.so # removing old chiapos rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so # reinstall plotman pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@development plotman interactive in plot logs you should be able to see Using optimized chiapos - 24288eb

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).