I noticed the product comparison page in your docs (Forge vs other software), which has been really handy already. I'm pretty new to the k8s ecosystem and its workflows, so this already really helped. I think it would be really great to also have a comparison with Weaveworks' Flux. since it seems to be a popular solution for Infrastructure as Code and CI/CD.
The main difference seems to be that Flux checks a single repository for the definition files of the entire environment and Forge takes a per-application approach. Because this different approach each solution has a couple of benefits that the other doesn't offer. So it should make for a really interesting comparison.
I noticed the product comparison page in your docs (Forge vs other software), which has been really handy already. I'm pretty new to the k8s ecosystem and its workflows, so this already really helped. I think it would be really great to also have a comparison with Weaveworks' Flux. since it seems to be a popular solution for Infrastructure as Code and CI/CD.
The main difference seems to be that Flux checks a single repository for the definition files of the entire environment and Forge takes a per-application approach. Because this different approach each solution has a couple of benefits that the other doesn't offer. So it should make for a really interesting comparison.