[racktables-users] Re: Uploaded files just 1 MB after download

Hi  Denis,

I see your point in storing all data in the database and for the simplicity
of the setup and maintenance I totally agree.
16 MB was for the test setup and I wouldn't go so far to store such a big
file in the database. But we have reports for all our installed servers
signed from the person in charge. Because of those I wanted to store the
scanned pdf files (sometimes about 6 MB) with the object. A perfect place
for the documentation of the installation.

The encryption example was just an example after all.

I think I can live with the limitation and just store those documents on
the fileserver.

Gretz killsystem

On Mon, 8 Jun 2009 14:49:26 +0400, Denis Ovsienko <pilot@xxxxxxxxxx> wrote:
> [...]
> 
>> Maybe a (optional) file based solution would be the best cause you could
>> separate the files from the database maybe to put them on a encrypted
>> disk
>> or somewhat.
> 
> Hello, all.
> 
> Well, Aaron considered storing files on the filesystem, when this
> feature was developed. I had insisted on putting everything into
> database that time, and still stick with the same opinion. The only
> problem by far are "large" files, and I think, experienced MySQL users
> can suggest a proper configuration for these (I personally use smaller
> files). There are benefits, which pay for that inconvenience.
> 
> A single mysqldump run includes all important data. Single RackCode
> setup controls normal access to all files (this isn't yet so for file
> previews, TBH). Encrypted media can be used on the MySQL server and/or
> SSL can be enabled for client-server connections. Once this is
> done, the administrator doesn't have to remember "the other" part of
> important data to protect.
> 
> There may be some "filesystem" file storage later, when all internal
> bits are justified for secure and reliable implementation of such.
> Until that happens we are likely to consider the size of an "essential"
> file as something, that can be easily achieved with MySQL (16
> megabytes?).

Other related posts: