1. I would say a lot of that depends on the specs of the server itself.
HD, RAM, etc.
2. I would think that obviously, keeping anything you wanted to back up
in one place would make that easier.  Make a partition just for the web
root and the custom tags directory.  Then just back up that entire
partition and only back up the system partition when you make changes to
configurations, etc.
3. Make the CF Server run as an user account instead of system and lock
down permissions as to what that account can do.  Disable any
potentially harmful tags that you're not using.  A lot of this depends
on if the sites are controlled by someone else (you're the hosting
provider) or if you're a one-stop-shop for web development/hosting.
Also, make sure you do proper stuff in your code like <cfqueryparam> and
checking file uploads to make sure they're not .exe or .cfm or anything
that could do stuff on your machine.
4. I'd say doing the separate partition will make it easy.  The rest
depends on the model you choose to follow for your app.
5. If everything is set up as a different site in IIS, you'll get
separate logs and can do a lot of monitoring that way.  As far as CF
monitoring of the individual app/site, I'm not sure.

I'm no expert, and may have just stated the obvious, but no one else had
posted, so I figured I'd give what I could.  I'm sure there's much more.

John Burns

-----Original Message-----
From: Dwayne Cole [mailto:[EMAIL PROTECTED]
Sent: Monday, April 12, 2004 11:36 AM
To: CF-Talk
Subject: Configuring New CFMX Box

I have and Windows 2000 server that I'm going to configure to host about
200 - 300 CFMX / SQL Server and Access websites.  

Each site will have its own set of templates (View and Controller
templates) but they will all share a set of templates (Model templates).

I have never had to worry about the server / administrative end of CFMX
and I'm looking for some suggestions on how should I configure the
server:

1). for optimal performance,
2). to ensure backup,
3). to secure the application,
4). to facilitate code maintenance and
5). to monitor the performance of the individual sites.

I looking for suggestion as it relates to partitioning the drive,
patching OS, removing example files, what should go in wwwroot and maybe
what should not, what supporting software should I look into.  

  

Dwayne Cole, MS in MIS, MBA
Florida A&M University
Certified Advanced ColdFusion Developer
850-591-0212
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to