← William Stewart

Deployment

Remap

Windows Server · IIS · GitHub Actions · Node.js

Available

Taking on work now

Case study

An application built largely with AI needed to actually run somewhere: two environments, one for the team and one the client could look at, on Windows infrastructure nobody wanted to administer.

What I did

Set up and now manage the server and IIS. Reviewed the code, fixed a session cookie that would have failed silently once the app was embedded in another site, and flagged that the only thing standing between it and a CSRF hole was a cookie setting. Then a GitHub Actions pipeline running against a runner on the box itself: merge to main deploys the team environment automatically, while the client-facing one stays a deliberate manual step.

Outcome

They push code and it deploys. The client environment only changes when somebody decides it should. I also traced a database that kept dying mid-deploy to the box running out of memory.

Detail

Remap were pitching for a piece of work, and the last stage of the pitch was showing a working prototype. I put the proposal document up first, then the two environments behind it: one for the team to build in, and one behind a login for the prospective client to look at. Set up across about two weeks at the end of July.

Windows ServerIISGitHub ActionsNode.js
Next

A site had been hacked. The first anyone knew of it was every page except the homepage returning a 404, with staff locked out of the admin.

Something similar going on?