remository:storage
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
remository:storage [2022/08/11 15:25] – created admin | remository:storage [2022/09/22 08:39] (current) – [Access Controls] admin | ||
---|---|---|---|
Line 3: | Line 3: | ||
====== Remository File Storage ====== | ====== Remository File Storage ====== | ||
- | The files in the repository managed by Remository can be stored in the database. When that happens, a file is split up into 64 KB chunks for manageability, | + | ==== Database Storage ==== |
- | Database storage is the recommended option, and is the default when Remository is first installed. It provides excellent security. Even if a file did have malicious content, it is incapable | + | The files in the repository managed by Remository can be stored in the database. When that happens, |
- | Each container in Remository has provision for setting groups that can do various things. The four options are upload, download, edit and auto-approve. You can enter as many groups as you wish. It is possible for Remository to manage the groups, but since Joomla introduced more flexible groups, it is normally more sensible to use the CMS groups. This can be selected in the " | + | Database storage is the recommended option, and is the default when Remository is first installed. It provides excellent security. Even if a file did have malicious content, it is incapable of doing anything while stored in a database table. (Obviously you still have to guard against serving malicious content to users of your web site). |
+ | |||
+ | Storing files in the database is secure and flexible, as it does not depend on quirks of hosting. Moving a site can be achieved entirely by moving the database tables and installing Remository. | ||
+ | |||
+ | When a user uploads a new file and automatic approval is not allowed, the new file is always stored in the database, irrespective of its final destination. That way, it cannot be used for an attack on your site. Only after the file is approved is it placed in the destination indicated by the file's container. | ||
+ | |||
+ | ==== Access Controls ==== | ||
+ | |||
+ | Each container in Remository has provision for setting groups that can do various things. The four options are upload, download, edit and auto-approve. You can enter as many groups as you wish. It is possible for Remository to manage the groups, but since Joomla introduced more flexible groups, it is normally more sensible to use the CMS groups. This can be selected in the " | ||
The first three settings are self explanatory. Auto approve is a little more complex. What it means is that when a user uploads a file, if the user is a member of one of the groups set for auto-approve, | The first three settings are self explanatory. Auto approve is a little more complex. What it means is that when a user uploads a file, if the user is a member of one of the groups set for auto-approve, | ||
- | Storing files in the database is secure and flexible, as it does not depend on quirks of hosting. Moving a site can be achieved entirely by moving the database tables and installing Remository. | + | === Storing files in the disk system === |
- | But it is possible to have the file store in the disk system. You can set this as a default in the " | + | But it is possible to have the file store in the disk system. You can set this as a default in the " |
Where files are stored in the file system, Remository will move them if the container is updated with a different absolute path. If the container' | Where files are stored in the file system, Remository will move them if the container is updated with a different absolute path. If the container' | ||
Line 19: | Line 27: | ||
A further choice can be made for files stored in the file system with the "Real With ID" selection in the " | A further choice can be made for files stored in the file system with the "Real With ID" selection in the " | ||
- | A software library exists that can make Remository file handling more abstract. It includes | + | === Amazon S3 file storage === |
+ | |||
+ | A new option is the ability to add more choices for storing the repository. The choice that is currently available is to use the Amazon | ||
+ | |||
+ | To use Amazon S3 you must create an account with Amazon for AWS services. For Remository, you need to set four fields in the " | ||
+ | |||
+ | To store data in Amazon S3, buckets are used. They are simply names. In fact, you can go further and use names that look like paths on a Unix-style disk system. So you could call your bucket " | ||
+ | |||
+ | The Amazon naming system, like the normal disk system, does not prevent name clashes. Just as with the file system, you can guarantee to avoid them by specifying "Real with ID" as described above. If that option is turned on, then each file will be placed in its own " | ||
+ | |||
+ | Using Amazon S3 gives you a lot of flexibility over storage (although you have to pay for it!). It also means that when a user downloads a file from your repository, it is sent to them directly from Amazon. That will normally be faster than sending from your web server. Again, there is a cost, but it is small unless you have a very large quantity of downloads. The use of Amazon clearly reduces | ||
remository/storage.txt · Last modified: 2022/09/22 08:39 by admin