In-memory persistence issues

[sleek shell]

Project ID: 6f683200-7f99-4ad6-9431-ffe6ca564062

Since Sets and Maps (with JS) are unable to retain memory for whatever reason (works perfectly fine locally) I was going to spin up Redis and use that for the data instead but for what ever reason I am unable to make another database. I created a new project (not the id provided) and it all works just fine. I'd prefer not to migrate to a new project just to fix this problem but if I have to I can.

I am on the free tier currently until it runs out then I'll bounce to the hobby plan. Unless there is a limitation on the amount of services per project on the free tier but after skimming docs and faq's can't find anything solid

[unreal shuttle]

Project ID: 6f683200-7f99-4ad6-9431-ffe6ca564062

[sleek shell]

No errors either just "Failed to deploy Redis" (for example)

[lethal pilot]

I'm away from the computer so I can't check your project, but are you perhaps running into the 5 service limit on the trial plan?

[sleek shell]

Possibly yes that would make sense, on the hobby plan what's the limit then if there is one?

Also about in memory data persistence, is this a designed feature on the trial plan that Maps and Sets etc are unable to hold data? Works perfectly normal locally (standard docker container with node 22 alpine)

[lethal pilot]

it's 100 services per project on any paid plan.

nothing wrong with storing temporary data in memory on any plan, of course since it's in memory it's going to be wiped when you redeploy.

[sleek shell]

Nothing persists at all, I've chucked a few console logs around and logged the contents of them and they are all empty despite being explicitly populated. Yes, all the variables are top level and it works perfectly fine locally but on railway it doesn't hold. To get better context, I use these for holding user id's temporarily for cooldowns, IP address for endpoint ratelimts etc so redeploys don't matter in this case.

If that makes sense.

[lethal pilot]

it makes sense, but I'll have to let the community involve themselves and help you with the application issues here, it wouldn't be related to the platform, a MRE would be best here.

[sleek shell]

Awesome

[sleek shell]

In-memory persistence issues

[sleek shell]

Update: managed to resolve this, it turns out it was a compilation bug that caused a critical file to not be compiled for whatever reason via railway. I've since fixed this.

[lethal pilot]

awesome, glad you could figure it out!