jeremy
Explore posts from servers413 Request entity too large (cloudflare)
I don't have any experiences with Cloudflare Tunnel, can't you upload to R2/S3 straight away without using the Tunnel?
Otherwise, this comment from your second link is the answer you are looking for "To work around, you can modify your code to upload large files in chunks each less than 100MB ...."
8 replies
413 Request entity too large (cloudflare)
First, I would say it's unrelated to Railway.
Are you uploading to R2? where did you see the 100MB limit? https://developers.cloudflare.com/r2/platform/limits/#account-plan-limits
8 replies
Add caching to Node Dockerfile
these articles (part 1 & 2) were pretty good walkthrough on how to reduce image sizes https://lengrand.fr/reducing-dockers-image-size-while-creating-an-offline-version-of-carbon-now-sh/
59 replies
How to disable cache with New Builder Environment
That worked, and also, build went from ~4min in the new beta builder, to ~1min with legacy builder. I thought living on the edge was the best.
I might just use the legacy builder for all my services again. Is there any date regarding this new builder to be the default?
8 replies
How to disable cache with New Builder Environment
Context:
I am building one of my service and it throws an "ENOENT: no such file or directory, open '/app/dist/.../file.json'" when starting the service, which fails and crashes the service.
I have 2 other services that use the same build commands and they also depends on this file, and it's successfully copied there during the build step.
I am expecting that something went wrong while building this specific commit and now I'm stuck with a "corrupted" cache.
The solution for now is deploying an old commit and it starting my service successfully
8 replies
Is there a way to translate my docker-compose file to a railway config file?
You would need to create separate services for each of them, docker-compose isn't supported yet
You might want to take a look at the marketplace to find pre-existing templates for the service you want to use.
- postgres: https://railway.app/template/postgres
- grafana: https://railway.app/template/anURAt
- prometheus: https://railway.app/template/KmJatA
I couldn't find one for tempo
Alternatively, you could write your own dockerfiles, eg. dockerfile.grafana, dockerfile.tempo, and so on, and point them to Railway
17 replies
HTTP logs for websockets
Maybe regarding httpStatus and txBytes, they could be hidden for websocket and/or have different color/label to differentiate http vs ws vs other protocols.
Regarding the request duration, I would personally want to see a single emitted message duration. My service emitted this message to the client, it took 1ms. That would be more meaningful for me. And not based on the client initialization duration, but not sure if that's possible on your side
12 replies
HTTP logs for websockets
okay I see, at least that makes sense why the duration is so long.
It's honestly a bit confusing. I would expect when I see a log entry that it counts for non-connection emitted messages. I don't know if it's possible or not. I know NewRelic is integrated within my codebase, but their data makes more sense to me when I'm looking at the logs. Seeing a websocket that has a duration of 200s doesn't really help me to debug/investigate if there is an issue, just my 2cent
12 replies
HTTP logs for websockets
What "round trip time" would mean in a case of a subscription/websocket, the time of the first connection (where
readyState
went into OPEN
) to the time the new message has been emitted, during the same connection? (I'm using this websocket library if that matters https://github.com/enisdenjo/graphql-ws)
I'm just finding this a bit weird, regarding the queries/mutations response times from graphql, it looks to be on par with what I see in NewRelic, around ~250ms in average, which is what I see in the HTTP logs. Regarding the subscriptions it looks to be way slower that's what I get on NewRelic, average is around ~2ms, and in the HTTP logs, I'm seeing a lot of these responses time being over 100s12 replies