El entorno Prod

Hey @elkuku ,

Did you try to clear the cache? Did you run all the required commands from the README file before start working with the start/ directory of the downloaded course code?

Cheers!

I doubt that clearing the cache would create the missing files but yes I ran the commands from the readme file (even the updated one...)

I am not sure what magic you have running on your end but as far as I understand the new asset mapper component it will only compile your assets in the dev environment while you have to run bin/console asset-map:compileto have your assets available in prod.

So.... What (the F) am I missing here??

Hey @elkuku ,

Sorry for confusing, I mean clear the browser cache, in Google Chrome you can do or while the Chrome dev tools panel is open, and you can press and hold the refresh browser button, then choose "Empty cache and hard reload". Though clearing the app cache is also a good idea, especially in prod as it may has some cached templates that were changed and so this may not include some necessary CSS files, etc. So I would recommend you both actually.

But once again, the steps you should do to boot the project with styles correctly:

1. download the course code
2. go to the start/ or finish/ directory
3. Run composer install
4. Run bin/console tailwind:build - this command is exactly the one that responsible for your styles look good, no matter of the Symfony env you're loading your app in.
5. Run the server with symfony serve or APP_ENV=prod symfony serve in case you want to run it in prod

I just re-downloaded the course code myself again, moved to the finish/ dir, and followed all those steps from above. After this, when I load the app in the prod mode - I do see styles, so no extra steps required for me.

Which OS are you on? Are you following this course from the start/ dir? Are you using Symfony built-in dev server to spin the app? If your setup is a different one, probably you may have some misconfiguration.

Btw, you may want to rerun the composer install command, does it fix the problem for you in prod? Because composer.json have some scripts that will be run during the install command. Or you can try to run them manually one by one to see if that will help.

I hope this helps!

Cheers!

Hey @Victor,
Thanks for your detailed reply. Very much appreciated. Unfortunately I am still not able the find the error on my side :(

About my environment: I am running on a Linux system with the Symfony binary installed and I did exactly what is recommended in the readme file. Everything works just fine in the devenvironment.

I think I disagree on your point number 4. On my system the command bin/console tailwind:buildwill build the CSS in /var/tailwind/tailwind.built.csswhich (I think) is somehow served by asset mapper in /public/assets/but only in dev...
When I switch to prod(via the .envfile) I get a bunch of 404s trying to load the assets from /public/assetswhich does not exist until I do a bin/console asset-map:compileafter which the site loads perfectly.

But... I have noticed after several tests that sometimes the browser loads the assets from the cache after switching to prodand sometimes.. not
Sooo.... All that I can think of at this point is that maybe your cache has not been cleared?
Please (please) correct me if I'm wrong ;)

Cheers!

Hey @elkuku ,

Ah, you're right, that's my browser's cache actually! I wonder if you're on Chrome too though, because it kinda should continue work well because of the browser cache. But indeed, when you manually clear the cache and do hard reload - the styles are gone. That's because the listener, IIRC AssetMapperDevServerSubscriber, works only in dev mode. So, for prod, you indeed need to run an extra command:

bin/console asset-map:compile

See more detailed information in Symfony docs: https://symfony.com/doc/current/frontend/asset_mapper.html#serving-assets-in-dev-vs-prod

Thanks for pointing it out, we will add a note about it.

Cheers!

I had the same issue!
Thanks for insisting ;-))