Bug 252272: Allow extremely large attachments to be stored locally
Patch by A. Karl Kornel <karl@kornel.name>, r=joel,colin git-svn-id: svn://10.0.0.236/trunk@175952 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
parent
23f85634a0
commit
52a301aa0e
@ -1,5 +1,5 @@
|
||||
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
|
||||
<!-- $Id: installation.xml,v 1.99 2005-07-09 22:37:26 mozilla%colinogilvie.co.uk Exp $ -->
|
||||
<!-- $Id: installation.xml,v 1.100 2005-07-12 10:56:52 mozilla%colinogilvie.co.uk Exp $ -->
|
||||
<chapter id="installing-bugzilla">
|
||||
<title>Installing Bugzilla</title>
|
||||
|
||||
@ -651,6 +651,14 @@
|
||||
'max_allowed_packet' or 'maxattachmentsize' value will not be
|
||||
accepted by Bugzilla.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
This does not affect Big Files, attachments that are stored directly
|
||||
on disk instead of in the database. Their maximum size is
|
||||
controlled using the 'maxlocalattachment' parameter.
|
||||
</para>
|
||||
</note>
|
||||
</section>
|
||||
|
||||
|
||||
@ -707,6 +715,13 @@
|
||||
to make a temporary copy of your entire table to do this. Ideally,
|
||||
you should do this when your attachments table is still small.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
This does not affect Big Files, attachments that are stored directly
|
||||
on disk instead of in the database.
|
||||
</para>
|
||||
</note>
|
||||
</section>
|
||||
|
||||
<section id="install-setupdatabase-adduser">
|
||||
|
||||
@ -234,8 +234,12 @@
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Attachments:</emphasis>
|
||||
You can attach files (e.g. testcases or patches) to bugs. If there
|
||||
are any attachments, they are listed in this section.</para>
|
||||
You can attach files (e.g. testcases or patches) to bugs. If there
|
||||
are any attachments, they are listed in this section. Attachments are
|
||||
normally stored in the Bugzilla database, unless they are marked as
|
||||
Big Files, which are stored directly on disk and (unlike attachments
|
||||
kept in the database) may be deleted at some future time.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
@ -774,7 +778,17 @@
|
||||
Content-Type (e.g. application/xhtml+xml), you can override this
|
||||
using a 'content-type' parameter on the URL, e.g.
|
||||
<filename>&content-type=text/plain</filename>.
|
||||
</para>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you have a really large attachment, something that does not need to
|
||||
be recorded forever (as most attachments are), you can mark your
|
||||
attachment as a Big File, Assuming the administrator of the
|
||||
installation has enabled this feature. Big Files are stored directly on
|
||||
disk instead of in the database, and can be deleted when it is no longer
|
||||
needed. The maximum size of a Big File is normally larger than the
|
||||
maximum size of a regular attachment.
|
||||
</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user