khalibloo
Explore posts from serversNodeJS Nixpack - GLIBC_2.38 not found
that would be a good workaround indeed. but i have so many env vars i'll need to copy over to the dockerfile. i wanted to see if that could be avoided.
as i understand, docker can't just pick up the env vars from railway. i have to redeclare each and everyone.
11 replies
RRefine
•Created by foreign-sapphire on 11/30/2022 in #ask-any-question
Invalidating the service worker cache
Yup, removing the API's cache fixed the issue. So I guess it was a combination of a service worker from a previously run app, and the API's own cache that caused it. Thanks very much
5 replies
RRefine
•Created by graceful-blue on 11/30/2022 in #ask-any-question
Invalidating the service worker cache
I used the default NextJS setup with the superplate cli to setup the project. The network inspector in the browser indicated that the response was coming from the service worker not the API.
But I took a closer look after seeing your message. I think the service worker might have come from other projects I had run previously on localhost:3000
I deleted the service workers. Now the network inspector no longer says "service worker", and it seems that I'm hitting the API. I'm still getting an outdated response, but now I suspect it's the cache I have on my API. Let me take a look at that and see if it helps.
5 replies