Thought I'd tap the knowledge out there on how you guys handle
administration of various circuit applications and the central application.
Alot of times you want to write circuit applications so that they can be
re-used in other applications. In addition, alot of modules have
administrators associated with them which manage content, data that the user
normally doesn't have access or has controlled/granular access to. Anyway I
was wondering how you people handle administration in FuseBox. Whether you
do it on a circuit by circuit level or do you write an admin circuit which
manages all the security and the admin fuseactions. Furthermore, how do you
provide standardized security for the circuits and their fuses. I know
we've seen the example where including the act_secure.cfm from the security
circuit provides the security. I suppose if you adhere to this standard or
any standard you're okay.
Goal: To create an application-wide administrator that centralizes site
administration
One Idea:
=========
Create a file that is a plain HTML menu (dsp_admin.cfm) that triggers the
various fuses like:
<b>User Functions<b><BR>
<a href="/secure/index.cfm?fuseaction=adduser">Add User</a><BR>
<a href="/secure/index.cfm?fuseaction=deluser">Delete User</a><BR>
Then have a script which crawls the applications looking for these
dsp_admin.cfm files and incorporate them dynamically into an admin center.
What are other developers doing out there?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
