I’m considering Netlify for hosting of my hobby website. I’m pretty happy with what I see, and using Netlify would push me to do couple of things I was planning to do anyway (like getting my images under source control). The Netlify-powered beta looks okay, and I’m currently looking at how my dev workflow would need to be changed to accommodate this change.
I was wondering whether there’s a way for me to diff two deploys. With the old way of serving my page (generate a
public tree, push it to serving via ftp), I’d keep the generated files permanently under source control so I could verify whether the changes I’m making are really what I intended to achieve. This also allows me to easily refactor different parts of my generator while making sure the generated content stays the same. The preview is nice, but it only goes so far in terms of confirming changes.
Example for my current setup:
In fairness, this is not a problem specific to netlify - it’s a general problem for sites powered by static site generators that don’t keep the output checked in. I can think of some sort of workaround: generate output at specific commit, save it to a dir, then, when needed, diff against it. This is an avenue I’d rather avoid if I can
Anyone else had a problem like that? :3