This is my feedback on https://studio.blender.org/pipeline/td-guide/workstations/maintaince In random order of me noticing things. Overall There is no introduction text for the page. It immediately goes into a sub-section, which is bad style. Better to explain what that page is to begin with, before diving into details. What is the scope of that page? Who is it for? There are various plural-singular mistakes. "Add-on" is written with a dash in the middle. Use links. This is a website, not a piece of paper. Why does everything have to be run as root? Doesn't this make it very sensitive to mistakes, as everything of the entire system is modifyable?

:::danger This is not official documentation, but rather a scratch-pad of ideas. Visit https://flamenco.blender.org/ for the docs. ::: Render Output To determine the render output location, some components need to be concatenated to form a path. It is important for Flamenco Manager to know the exact file paths that will be written, at least down to a pattern like /some/path/to/*.png. That way it can do things like automatically creating a preview video from rendered frames. Ingredients

Almost 5 years after the release of Flamenco 2.0, development has started on a new version: Flamenco 3**. In this blog post Sybren Stüvel describes the current vision on Flamenco 3, with the intent to discuss this with anyone interested, get feedback, and improve the design. Flamenco is the Open Source render farm software, developed by Blender Animation Studio. It is aimed at performing tasks such as frame rendering, and video encoding. It supports any Blender version, hardware configuration and any other software with a command line interface. Target Audience Flamenco is meant for smaller animation studios and individuals at home. Think of roughly 1-10 artists using it, and 1-100 computers attached to the farm to execute tasks. Blender Animation Studio uses various desktop machines for the render farm when they're not used by the artists, and some developer machines are powerful enough to run Flamenco and work on coding Blender at the same time. Design Principles

End users are both artists and TDs. Farm Management Downloading and installing Flamenco Manager Downloading and installing Flamenco Worker Configuring Flamenco Manager job types / customisation storage locations

MongoDB to relational database Moving forward I want to get rid of MongoDB. It's been bundled with Flamenco Manager for ease of deployment, but it's never gotten really stable. Database Choice ❓ PostgreSQL: good, fast, real database, but requires installation. I've never done that on anything but Linux, so not sure about how simple/hard that is. Pure Go bindings, making cross-compilation easy. ❓ SQLite: Go bindings require C compiler, making cross-compilation hard. Pure Go bindings available. Requires no installation. Easy to start from scratch, but can make Manager upgrades slightly harder (need to copy database + config file around). Database Interface