liwords VS Caddy

Check out https://woogles.io (disclaimer I am a cofounder). AGPLV3 platform with world class bots, puzzles, a free analyzer, clubs/tournaments, and more to come. You can see the source code at https://github.com/woogles-io/liwords. We recently hit 5M games played and have hosted a few major tournaments.

A small team of us work on a project https://github.com/domino14/liwords - this is an online crossword-board-game playing website. We have around 6000 MAU, are fully free and open-source, and need a lot of coding help!

We built woogles.io (a crossword board game playing site with almost 10K MAU) in Go. See https://github.com/domino14/liwords

https://github.com/domino14/liwords - warning it’s not that well-developed but it’s ok

A small team and I made https://woogles.io - we were inspired by lichess to make a site to play crossword board games during the pandemic (like Scrabble, Words with Friends, etc).

We did raise money on Kickstarter - 25K but are purely donations-driven and open source (AGPL3) Most months we just get enough to cover the cost of running the servers. We have around 6000 monthly active users, have hosted several big worldwide championships, have puzzles, and just earlier today released a board editor / broadcast mode for annotating real life games in real time. We also have a top notch bot AI and WASM-based analyzer.

Our stack is Go, Typescript + React, with NATS/PGSQL on the backend.

woogles.io

The people behind those websites and apps have no clue this software exists. The exception is woogles.io because it is associated with the Macondo AI. /u/14domino is the brain behind both of those things

https://woogles.io raised $25K on Kickstarter and built a more beautiful site. Come join us (we’re still taking donations :)

- Playing online: there is woogles.io which I personally would recommend; it's made by players for players and is free to use. Among the features are: play against humans, play against strong bots, tournaments, feedback on your moves after the game, availability of different languages and game variants. Other options are: playscrab.com (also made by players for players); isc.ro (the Internet Scrabble Club); the app Scrabble Go and, if you don't mind playing with slightly altered game rules, Wordfeud, which comes along with a large online league (not technically affiliated with the app itself).

No, look at the associated unit test: https://github.com/caddyserver/caddy/blob/c6eb186064091c79f4...

If that test fails we could serve PHP source code instead of having it be evaluated, a major security flaw.

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

I think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/