Question

Is there a way to allocate a certain amount of space to a topic/catagory and a certain amount to a subcategory?

i.e. rodents have 5mb max. Mice, a subtopic, have 2mb max. etc...

If there isn't support for this, would it be easy to add?

• TWiki version:
• Perl version:
• Web server & version:
• Server OS:
• Web browser & version:
• Client OS:

-- AmitBeh - 18 Jun 2003

Answer

There is no support for this in TWiki.

You could create a Plugin that checks for disk space used in the "before save" callback hook.

-- PeterThoeny - 18 Jun 2003

As Peter says, this is not a TWiki problem it is a system problem. How you solve it will depend on the facilities that your ssytem offers and where and how you want to administer it.

Suggestions:

First, clarify what your needs are:

• Do you really need revision history? It can eat space and some business policy doesn't need it.
• Is your concern over space for topics or space for attachements?
  • If attachements, what is your bsuiness policy for keeping revisions of the attachements?

Now under HP-UX/DG-UX/AIX/UNIX/Linux you have space administration tools such as

• Disk space quotas. This may not be easy if all the files are owned by apache.apache, but there are workarounds, they just take a lot of planning and set-up.

• Mount file systems at the key points under twiki/data/ and =twiki/pub/=
  Again this requres planning and administration. I use this technique in AIX and Linux-with-LVM where its easy to create new file system volumes or grow older ones to match demand. I've used this technique in other settings, for other projects (a spool/cache manager) but so far haven't had to use it for TWiki. I'm fortunate in that my TWiki client-users have ample disk resources.

One of my projects is to convert the storage management of Twiki to OO. Realy a "web" is a contianer of "topics". The Web doens't need to to be a (local) file system, the topics could be stored anywhere anyhow. The extant Meta.pm modules shows how topic metadata can be isolated by OO techniques. Seperate storage also addresses the issue of mirroring and sharing in a corporate setting.

-- AntonAylward - 19 Jun 2003

Thanks for the feedback guys. I was thinking of space for BOTH attachments AND topics. I think we'll probably save old attacments somewhere else...perseus or something else...im not sure, Im an intern here

As for the revision history, I think for now we do need it. It was one of the reasons we decided to use TWicky, but who knows how this will turn out a month from now. Thanks for the suggestion.

I might get back to you when I get more information, but for now I'll work with what I have.

Anton, your project on seperate storage sounds cool, good luck with that. We're thinking of where to store data...

Thanx again guys

-- AmitBeh - 19 Jun 2003