Rails app failing on rails s about jumpstart HOT 11 CLOSED

assets:precompile is only used for production. You need to run bin/dev for development.

from jumpstart.

Appreciate you Chris

interesting, I cant get jumpstart not to error on my local system without it.

from jumpstart.

cssbundling-rails and jsbundling-rails use separate processes to build assets, so you can no longer run just the rails server.

from jumpstart.

so when starting a rails server i have forman running, and I have bin/dev what else do i need to run to not have to precompile?

from jumpstart.

You probably need to clear out those precompiled files if you ran that.

from jumpstart.

ok, maybe a better question is... when you start a local with jumpstart, whats your process?

from jumpstart.

I just run bin/dev

from jumpstart.

Yeah cool, i will have to do some more research, but when you google error starting jumpstart its a thing, and its always the css. https://gorails.com/forum/error-starting-new-jumpstart-app

from jumpstart.

Well if nothing else hopefully this is a great spot for it.... dont start your server with rails s or rails start. simply replace it with bin/dev for applications using cssbundling-rails and jsbundling-rails.

from jumpstart.

That's why I included it in the instructions here:

Just tried it on a brand new app and works fine for me.

from jumpstart.

I get it now, and it makes complete sense.

The issue i had was that when i first ran it it failed.

I had to watch your https://gorails.com/episodes/esbuild-jsbundling-rails to understand why and add the "build": "node esbuild.config.js" to the package.json... so by the time I got there...

sounds pretty dumb but - bin/dev didnt really play into my mind as the way i was starting the server.

I am not sure how often you get this, but adding "- to start the server", might save you time and a-lot of people a-lot of heart ache.

Regardless, i appreciate your work, and you are a big part of my rails journey.

from jumpstart.