Thanks for the suggestions. IP tables or firewall is not really appropriate since I still want users to see the "unavailable" page, not completely block them.
.htaccess is the easiest for one off manipulation, though it would be nice to have the feature self-contained in the framework and not have to futz with .htaccess. I'll give it a whirl with index.php to filter out the IP and redirect to the unavailable page. On Mar 20, 2:55 pm, Lee Bolding <[email protected]> wrote: > Why not take a look at the IP exclusion clause in the dev controller > and modify this accordingly? > > Make a backup of your existing index.php, then copy the dev controller > to index.php and add your exclusions. > > Or, as Sid said - use .htaccess > > Or iptables. > > Or a firewall. > > Many ways to skin this particular cat :) > > On 20 Mar 2009, at 09:32, CiPheR wrote: > > > > > Is there a way to "disable project" but allow only specific IPs to use > > the site? This is very useful for performing post-install validation > > so that testers can validate the new release without necessarily > > opening the site up to the public. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
