54 Replies
Project ID:
6d888c30-44bb-4d6c-8df0-b37ecd39e975
6d888c30-44bb-4d6c-8df0-b37ecd39e975
just abort it and try again.
also, this isn't causing the problem you are currently seeing but, please don't run your app in preview/dev mode on railway, it will just be headaches
thnx for the tip
slower response times, increase in ram and cpu, instabilities
retrying doesnt work for me
okay, i have notified the team
same here
I checked but its weird naming preview is the production build
this is a mono repo right?
yes
/*
* WHAT IS THIS FILE?
*
* It's the bundle entry point for
npm run preview
.
* That is, serving your app built in production mode.
*
* Feel free to modify this file, but don't remove it!
*
* Learn more about Vite's preview command:
* - https://vitejs.dev/config/preview-options.html#preview-options
*
*/Vite
Next Generation Frontend Tooling
what framework are you using?
qwik
but with nx-qwik
does it build a spa?
that does client side routing
yes
but without downloading the whole spa from the start
does the build folder only contain a single html file?
the build folder "dist" doesnt have a html file
interesting
I have no experience with qwik, so I will look into an appropriate way to run your app in production mode on railway and get back to you on that
the two support engineers aren't active right now, so please be patient
and sorry for any inconvenience this may have caused
Its fine
but qwik is really fun would really recommend it
yes really fun
ive never seen docs for a framework that tell the user to figure it out themselves
hahaha I feel like thats because qwik is very new (1.0 is out for just a month) these rough edges will improve over time
but its pretty weird indeed
my problem with the build stuck on metadata is fixed
its still building but it is going further than before
can you show me a screenshot of your service metrics?
sure
may 21 until now
please show me the service metrics from the metrics tab of your service
set to 6h
oof
thats what 550mb? this is why you dont run preview/dev servers on railway
but the dev command is a different one
i get that its a lot
dev or preview, they mean the same thing essentially
1. run
npm run qwik add express
2. cut and paste the start
command into the dev
command
3. cut and paste the serve
command into the start
command
4. remove the now empty serve
script
5. push changes to github
6. ram usage should now be under 100mb!!I will look into it
please do, 550mb is absurd
@Brody Since I used nx it took a few extra steps but i got it to work and indeed its a lot better now. thnx for pointing it out to me
now its like 210
that's still quite a bit, do you mind sharing your package.json for the qwik app?
Sure
interesting
can i see the main package.json too?
or wherever you have the qwik start command
this is the main package.json the commands are in project.json that one looks like this:
on prod i run serve.express
and how are telling railway to run
serve.express
?npx nx run dashboard:serve.express --host:0.0.0.0
and you just set that as the start command in the service settings?
i need to improve the watch paths
correct me if im wrong, but doesnt that build twice??
yes it does
why is that desirable?
no just a mistake
all you would have to do is remove this, right?
yes
im going to give it a try
one of the 2 was at 269 before and went to 208, the other was at 190 and went to 195
aside from building twice, as far as i can tell you are running it correctly, so it is what it is
the joys of JavaScript
Its worth it for me 🙂
Thnx for your help
so all is good?
Yes perfect
awsome