El entorno "prod"

Hey @Domingo987

That's odd. From the error, I believe you're not loading the TwigBundle for the prod environment. Check your bundles.php file to see if it loads that bundle. Also, I may recommend to re-install your vendor directory

Let me know if that helped. Cheers!

Thanks for suggestions but nothing will work. I've done a composer update, I've checked the bundles, cleared the caches.
I work with Symfony since Symfony 4. Its the first time that the prod environement will not work as the dev.

I put here the log :

[PHP-FPM    ] {"message":"Authenticator does not support the request.","context":{"firewall_name":"main","authenticator":"App\\Security\\UtilisateurAuthenticator"},"level":100,"level_name":"DEBUG","channel":"security","datetime":"2023-05-09T08:00:22.966375+00:00","extra":{}}
[PHP-FPM    ] {"message":"Uncaught PHP Exception Twig\\Error\\SyntaxError: \"Did you forget to run \"composer require symfony/twig-bundle\"? Unknown function \"dump\" in \"actualites/actu_detail.html.twig\".\" at /Users/symfony6/town/vendor/symfony/twig-bridge/UndefinedCallableHandler.php line 93","context":{"exception":{"class":"Twig\\Error\\SyntaxError","message":"Did you forget to run \"composer require symfony/twig-bundle\"? Unknown function \"dump\" in \"actualites/actu_detail.html.twig\".","code":0,"file":"/Users/Sites/symfony6/town/vendor/symfony/twig-bridge/UndefinedCallableHandler.php:93"}},"level":500,"level_name":"CRITICAL","channel":"request","datetime":"2023-05-09T08:00:23.532817+00:00","extra":{}}
[Web Server ] May  9 10:00:23 |ERROR  | SERVER GET  (500) /actualite/first-time ip="127.0.0.1"

Thanks for any suggestions

Interesting... Have you checked your config and service files for some weird, prod-specific config? If that's not the case I believe the error message is misleading. Try disabling xDebug, it sometimes causes a weird behavior

I am an "end user". I have started a new project from scratch. For the moment the dev and the prod work both well.

Thanks for your help.

Hi @Delenclos-A!

I'm absolutly disappointed.

Well, we don't want that. So let me see if I can help :). And yes, I think I can see the problem! We CAN solve this problem with a tweak in your Webpack config. But actually, I can suggest a (hopefully) better solution overall for you.

Ok, so the site is installed at http://potcommun.lamih.fr/public/login. The key thing I notice is that the public directory is in the URL. Even ignoring Webpack, that isn't ideal. I'm guessing it would be much nicer to just have the URL be http://potcommun.lamih.fr/login. This would also fix the Webpack problem.

On your host, you probably have a document root directory which is available to the public - let's pretend it is /var/www. And so, you've deployed your app into this directory. This means you have a /var/www/public directory with your application's index.php inside of it. That's why you need to have the extra /public in the URL: that executes the /var/www/public/index.php file.

To remove the extra public, you have 2 options:

1) If you have access to your server configuration (e.g. Apache, Nginx, etc) and are able to, you could change the "document root" from /var/www/ to /var/www/public. This is really the only directory that should be public (right now, your entire project source is public - e.g. https://potcommun.lamih.fr/webpack.config.js

2) Or, an often easier way is to use a symbolic link. That looks like this:

A) Deploy your app to some OTHER directory that is NOT served by your web server - e.g. ~/potcommun.
B) Delete the web root - so literally rm -rf /var/www
C) Create a symbolic link from /var/www to /potcommun/public. The command is:

cd /var
ln -s ~/potcommun/public www

With this setup, your document root will STILL be /var/www. But that is a symbolic link to the public/ directory of your app.

Please let me know if this helps!

Hi, great answer. Thank's to take time to help symfony's community. It works fine. I've changed the document root and it's just magic.

Have a good day and Thank's

Hey @Anatolie

I'm guessing you forgot to clear the cache for the prod environment. Could you double-check that?

Cheers!

Of course I cleared the cache.

That's odd. If you change something else, do you see it reflected?

Hey @Yulong!

Hmm. I'm not sure what happened in your situation, but normally you would need to switch steps 1 and 2. The idea is:

1) Edit .env file to switch to prod (at this point, if you refreshed, you WILL likely get a 500 error).
2) php bin/console cache:clear - because .env is set to prod this will clear the prod cache. If you did this step before step 1, it would be clearing the dev cache, which is something you can do, but it wouldn't help in the prod environment.

Anyways, I'm sure it was something minor - I just wanted to give you a bit more detail about the "why" behind the order of these steps. Btw, you can also run php bin/console cache:clear --env=prod to clear the "prod" cache, regardless of what APP_ENV is set to in .env :).

Cheers!