luke.b//blog

Things I want to do with my new CMS-over-git (name tbd):

  • deploy all apps
  • deploy all apps using Dockerfiles instead of a shell script?
  • deploy nginx config for the reverse proxy?

After that I can deploy entire apps + infra with a single commit. But probably more like 10 commits of “work… please work… work now please…”

I feel inspired to write all weekend. And maybe it’s time to get that photo journal up that I’ve thought about recently.

I also want to do some more personal writing.

New margins on stuff and new raw log navigation is looking good.

It took me about 30mins? But I managed to switch link-scrabble over to the new regime, so now I can deploy changes to it by pushing to the remote repo! :)

Next I’ll do instascrabble, and then probably my website.

I’m already regretting not using some kind of dockerised solution for this though - building stuff outside of docker containers seems a bit restricting. I suppose there’s nothing stopping me from giving each project a Dockerfile and then making the build.sh script use that instead.

That way I wouldn’t have to rely on hugo or yarn or anything else being installed prior to things being built.

Just checking this thing still works!

Other cool thing: I’ve been using nomad all day and it has handled a remote ssh terminal without too much pain at all.

I’m loving the new full-screen mode.

https://github.com/lukebarnard1/nomad-term

So it took all day, but I finally have a single command to open Vim, commit the new file to the local repo and push the change to the remote repo. This will trigger a post-receive hook on the server which runs the build.sh script in each project directory where files changed!

CMS over git! :D

This is cool. I want to expand this to my other deployed projects like my personal site which is a React app, and a couple of other React apps that I’ve been hacking on recently.

The API is so simple so I don’t anticipate any major struggles. There’s still a little bit of extra work when it comes to adding new projects though because I’m currently not building project artifacts directly in a directory that is being served by nginx - there’s one level of symlink indirection that isn’t automatic (mostly to be cautious and to avoid exposing something unintentionally).

I definitely want to get to a point where a single git push can deploy an entirely new app though, this would be awesome :)

OK I think it works, it’s only rebuilding my blog when the blog content changes.

Come on. Work.

And again?…

page 23 of 27 after before