Introduce [My Chia Farm] beta



This is beta version and developed for Linux only for now. Support for Windows and Mac will be added in the future. The primary focus was on plotting process managing, automating and optimization. And yes, second focus will be on system resources monitoring. But, whole platform concept gives more flexibility, not only plotting. I have some ideas which way to develop this project (see below) and, of course, community demands and wishes would be realized to the best of my ability.


  • Accessible via internet from anywhere (with configured apache/nginx webserver)
  • Built-in webserver for local running
  • Nice GUI

Plotting manager

  • Flexible event driven plotting manager for multiple configurable jobs. Next seeding could be started on any stage of plotting process.
  • Each plotting job could be limited by total number of plots to be done and number of workers doing this job.
  • Supports CPU affinity setting
  • Supporting both original chia plotter and MadMax plotter and ready to be adapted to any other plotters and changing of existent plotters
  • User input validation and checking for required parameters
  • Executing custom command before plotting process started
  • Executing custom command after plotting finished (%plot% tag would be replaced with absolute plot filename). For example, you can make command to upload plot file to network storage.
  • Replotting. The one earliest plot (up to specified date) in destination folder could be removed when seeding process begins.


Click here to view screenshots

Job preview:

Job configuration:

Plotting progress view:

Other functionality would be added as soon as I can do this.


We love screenshots of the GUI, can you post some?

1 Like

Thanks, screenshots added

Wow nice!

Time to start my migration from my gaming pc to dedicated ubuntu farmer.

One question… Where is dark mode button?

haha jk jk.

1 Like

It is in TODO list :rofl:

woo finally somone 0n task… haven’t installed yet but this seems great.great concept and idea. ben waiting and waiting for someone to develop something like this.
just trying to understand how to implement. I
s this for full nodes? plotters? or harvesters?
does it show active connections from farmers and harvesters?
does it interpret logs? I get its a plotting manager
but I run all my services in separate containers. can this unify all of them in a web gui
orrrr??? can we get some screenshots of this beautiful gui??

Tanks for feedback! :partying_face:

In future I hope this project will become full-featured “chia control center” (or fork of chia). But it will take some time.
I’m planing to add and improve features one-by-one, so realized ones can be useful and can work today, not waiting for the whole project realized.

My initial goal was to do plotting manager with features I wanted. And one of these features was remote accessing to it. I found different RDP client-server solutions or similar controlling systems takes a lot of system resources sometimes or have some system-level troubles, such as handling Wayland on fresh Linuxes. So I decided to make web-server app to minimize these ugly dependencies. And next thing I thought: “Holy crap! I could have web-interface for the whole node!”. :rofl:
That’s way this architectural concept was born.

For now only plotting manager has been implemented. But there is some sweet features for near future.
Coming replotting process would not be hurt with option I realized:

And another feature I wanted is custom commands execution, so there is no need to run some side scripts to move plots (for example) to network storage or something else.

It took a lots of time to make this manager (handling several different plotters and its future changes).
For now I would have several days vacation and continue my work on chia log analyzer and notifications system. I thing it’s more important for now.

P.S. screenshots is under the cut (check “Click here to view screenshots”) in first post

At top right corner after you update project with git pull :sunglasses:

There is some documentation now: