Here is the localhost/vps deployment if anyone wants to test it : https://github.com/scripting/rss.chat/issues/2
This is fantastic! And it’s very well documented, complements to you and @claude!
Thanks Scott, that's high praise. :-)
I just finished my installation and the new server, demo.rss.chat, is up and running.
We have more excellent stuff in the pipe, still working out some details.
Also the worknotes.md files are working now. Claude is doing all the change notes there.
Still diggin as they say.
I like when I can contribute with approaches I do at work but for open-source projects :)
and Yes Claude is a great team mate to have around !!
Hi Scott — the server install just got simpler. Feeds now live in the database and the server serves them itself, so there's no S3 bucket and no AWS account in the setup anymore. install.md and config.md are updated to match. Since you've done this install for real, would you give the new instructions a read and tell us how it goes?
OK, I'll put an agent on it. 🕵️♂️
As a test we're doing a straight install on a new, throwaway server. node is installed locally using fnm, and I've asked Claude to install mysql and caddy with docker.
We have to teach my Claude to do that too. We keep coming up with how useful it would be for it to have a throwaway instance to test with. I don't have the bandwidth to branch out into that area. Usual story. ;-)
You guys know about /init command for claude right ? usually you do this in our own repo, claude will fabricate a claude.md mostly for him, even tho you, as a human, can obviously drive what's in it, this is where you can specify some preferences too and if you commit it to the repo, then your contributors also get to work under the same paradigm with their claude
there you can have a docker or deploy section, where you define how the code should be run either node native way or docker based approach, once everything is in place, you can have custom /commands to actually deploy your code the way you want and claude will follow the exact instruction, you can grab a coffee instead of teaching claude the same stuff over and over again :)
Short answer: it worked. 😃
Claude did find a couple of stumbling blocks (it didn't know what port needed to be proxied, and there was a websockets error logged that wasn't really an error), but I'll write issues for those.
That was fast — thanks for the real-world test. The port gap is already fixed: step 8 of install.md now says the server listens on 1420, and that websockets have their own port. One detail worth knowing: the websocket default is 1422, not 1462 — 1462 is just what this server happens to use.
We did another test install with the updated docs. The agent picked up the port right away. It also suggested updating the docs to mention using "flUseMySql2": true with MySQL 8 and posted an issue at https://github.com/scripting/rss.chat/issues/10