cachebox folder placement?

[Mike Henke]

I think, the intent was for cachebox to handle several application's
caching, so I placed the cachebox folder on the same level of the
webroot (c:\webroot and c:\cachebox) and used a cf mapping for the
cachebox folder. Does this seem correct? Or should I drop it in the
webroot?

Then will I have to setup the polling or something to recognize each
application (lets say each application is a folder under webroot)?

Thanks,

[s. isaac dealey]

> I think, the intent was for cachebox to handle several application's
> caching,

Hey Mike,

Yes, the thinking is that the ideal situation is to have a single
CacheBox management application for the entire server (although that
may be problematic with shared hosting, in which case it's possible to
break the rule and create a service for just your domain).

Having a single service for the whole server means that although the
approximations of memory usage will never be perfect, they'll be more
accurate when all the metadata is in one place.

> so I placed the cachebox folder on the same level of the
> webroot (c:\webroot and c:\cachebox) and used a cf mapping for the
> cachebox folder. Does this seem correct? Or should I drop it in the
> webroot?

There's nothing wrong with that.

I have mine inside the webroot and rely on the server's default /
mapping, but, I noticed that when I create a project where the apache
root for the vhost is in a subdirectory, that moves the default /
mapping and it can no longer see /cachebox from that default mapping.

So using a mapping in the CF Server Admin will resolve that issue
without forcing you to create an application-specific mapping for each
application. (And is probably actually the better solution in the case
that you have several vhosts for different domains.)

> Then will I have to setup the polling or something to recognize each
> application (lets say each application is a folder under webroot)?

You should only need one polling task for each instance of the CacheBox
admin, rather than for each application. So if you've got 5 applications
on your server and they all share a CacheBox service (optimal), then
there should only be the one polling task for that CacheBox admin app.

Part of the reason I had my cachebox in the webroot is that it seemed
more convenient to use http://localhost/cachebox/ as the default URL
for the admin application, as opposed to creating a new vhost for it.
And if it has its own vhost you will have to create a config.cfc so you
can overwrite the polling URL to hit your vhost instead of localhost.

--
s. isaac dealey :: AutLabs
Creating meaningful employment for people with Autism
http://www.autlabs.com
ph: 817.385.0301

http://onTap.riaforge.org/blog