cuttle VS gitlab

I got started in web development by building a full stack web app to play my favorite card game, Cuttle, pvp. Now that I'm working in the industry, I've open sourced the project and I continuously improve it with the help of other contributors. Here's the live deployment and here's the code.

The app is live at https://cuttle.cards and actively in (modest) use. We are continuously improving it, and you can practice essentially any part of the full stack by contributing. Here’s the code. The app is a Vue3 SPA with a nodejs backend (using sailsjs), and a postgres database, and we use cypress for the bulk of our automated testing.

Everyone is welcome! The best way to get started is to join us on discord where you can chat with me and the other devs about setting up and picking your first issue. Otherwise feel free to grab any of the issues on our github!

For one thing, you're welcome to join our discord where you can chat with me and other contributors (players too). I'd be happy to help you find a first issue to contribute. Regardless, feel free to check out our issue list to see if there are any you'd like to take a crack at.

For what it’s worth, I’ve open sourced my project (here’s the code) so if anyone would like to practice full stack web development skills by working on the oldest known combat card game, come check it out! We have five tournaments every year and open play sessions twice a week so your contributions will be used by real people in a live environment

Here’s the code

Cuttle is my favorite card game and I learned web development by creating cuttle.cards: an open source, fullstack pvp web app where people can play Cuttle online, for free! The app uses a postgresql database, a nodejs backend and a vue3 front-end. Here's the code.

I use websockets in my card game project: cuttle.cards as the way of updating all the players when someone makes a move. Here’s the code.

It’s a full stack web app with a Vue frontend and a nodejs backend built with the sailsjs framework. Here’s the code. The project is open source and under continuous development to improve the player experience.

We don’t have the full team structure that you’d see in a professional setting, but we have 5 core engineers including myself who work consistently on the project and a number of other contributors at various levels of experience. Here’s the repo. If any of that interests you, hit me up!

Since the relevant code appears to be in the "ee" directory <https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.0-ee/ee/l...> and is not present in the foss repo, I'm guessing the answer is no, at least for now. They do have a history of "releasing" features from EE back to CE but my suspicion is not for LLM stuff

(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)

and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...

and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)

This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...