luke.b//blog

Let’s try that again…

OK this should work now. It should only try to build the projects that were changed.

Oh I could just push empty commits…

I’m now trying to trigger the thing to give me a sign that the git diff can be used to indicate which files have changed …

I think the next step would be to figure out how to only build projects that have changed since the previous commit instead of rebuilding every deployed project in the mono repo.

It worked! And now my script for writing a log entry also automatically pushes the newly written blog entry.

This is too cool.

This log should be automatically be deployed when the commit is pushed upstream!

I have set up the remote repo and it now runs a post-receive script when it receives updates. The script checks out the latest tree into a directory ready for the build step.

I used this tutorial for pointers.

And it’s back!

Right. I’ve set up a git repo on my server! Time to see if I can push changes to it.

I’ve just realised my normal blog has disappeared so that’s good.

page 24 of 27 after before