Home/ Questions/Q 6909111
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:38:51+00:00

I want to provide a dev-environment on the production server for my Symfony 1.4

  • 0

I want to provide a dev-environment on the production server for my Symfony 1.4 projects. Reasons:

  • Allows me to get details of errors, etc.
  • It happens very often that I get different output on the prod-server and on my private development server. This is due to different server configuration, php extensions and available data.
  • Sometimes my client wants to see small changes quickly. I don’t want to clear the cache until changes are available
  • The most important point: I want to be dead certain that no “cache-magic” is going on when problems occur on the production server.

A bad idea would be to make /frontend_dev.php accessible for everyone.

Also, I can’t use sfGuard, since the dev-environment must be accessible regardless of whether I’m logged in or not.

I’m running my projects on Apache 2. Maybe there is a solution using htaccess.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In frontend_dev.php just use HTTP authentication to protect the file

    Or in .htaccess (or vhost file) you can do this to protect your frontend_dev.php script:

    <FilesMatch "frontend_dev.php">
   AuthName "Restricted file"
   AuthType Basic
   AuthUserFile /path/to/file/.htpasswd
   require valid-user
</FilesMatch>

    EDIT: And if you’re using the command symfony project:deploy production --go to deploy your project into production, be sure to change the rsync_exclude.txt file so it copies over the frontend_dev.php file too.

    • 0