In this dev log:

• my experience “managing” the library, tests, CI, coverage, code analysis, publishing (yes, it’s on npm 🙃, though I don’t recommend playing with it yet)
• automation, testing and more testing

Moving into the cloud…

I’ve received an email from my vhost company that they’ll move my account up one tier and in effect double my invoice. Hmm 😱 By the instinct I searched for alternatives for hosting my games portal. Already had some experience with AWS (lonely S3 buckets) so what the hell, let’s go. If I’m going to seriously consider it my “life’s goal” then I should commit to it as much as I can.

• bought the domain! https://cardgames.world - nothing’s there yet!
• setup servers at AWS using Terraform configuration
• portal automatically deploys to test servers when I push changes to develop branch

Continue reading

Okay, so looking at my last dev log, a lot has changed.

It’s not a game anymore

The more I coded, the better I realized that it would be better to start chopping this one big project to separate pieces:

• CardsGame libraries - both client and server side in one place as one big happy monorepo family.
• Cards game “portal”, a thing which is using CardsGame libraries to provide some games for players.

CardsGame libraries are intended to be a set of tools initially for myself, but could also become a tool for other people in the future. Colyseus is still the main driver of network connectivity here (I even managed to contribute with some bug fixes for them 😇).

So what happened between now and then?

Continue reading