It would be useful to have a section in the docs that discusses the practical aspects of setting up and maintaining an sstate cache mirror, since there are a few gotchas. Some points to consider: * How to configure it * How to share it * Arrangement of machines for a build farm or team of developers * Keeping size under control (multiple approaches?) * Ensuring siginfo files are synced before tarballs * Troubleshooting issues (e.g. how to recognise host contamination - at least make people aware that it can be exposed more readily) * Other services that need to be alongside e.g. PR server, hash equivalency, etc. * Limitations
I meant to mention - I thought we had a section similar to this already but I could not find it in the reference or development manuals.
We don't have this Paul. Someone could provide some rough info and I can get it in. Scott
Bulk move of 5.1 M4 to 5.2 M2 as approved by AlexB.
Bulk move of bugs I am assigned to from Milestone 5.2M4 to 5.3M1.
Sent a series to document this: https://lore.kernel.org/r/20260722-sstate-mirrors-doc-v1-0-570baeb41c32@bootlin.com
Series merged: https://git.yoctoproject.org/yocto-docs/commit/?id=15b08adf30ddbeb9f9911d4a6ae207e95f94ca87