[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cgiapp] Site layout best practices question


In the best practices section of the CGI::Application web site, there is a discussion on site layout as follows:

project_name/
       htdocs/
       modules/
       templates/
       devdocs/
       conf/
       bin/
       externals/
       logs/

I've set up a project with this structure and I like working with it so far. I've also used environment variables in the virtual host block like the example below:

# for perl to find my local modules
SetEnv PERL5LIB /path/to/project_name/modules

# for C::A and H::T to find my templates
SetEnv HTML_TEMPLATE_ROOT /path/to/project_name/templates

# for scripts to use as the base dir for data files, uploads, etc.
SetEnv EXTERNALS /path/to/project_name/externals

# for DBI to find a database connection
# DBI_DSN and/or DBI_USER may also be defined here

Now I'm starting to get ready for deployment and have turned on Taint mode with the -T option of the instance scripts and need to untaint the the environment variables. Is there a best practice for this?

Ed Pigg

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed


Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.