The next big feature of CYPEX we want to focus on is the ability to upload files. Files are stored in the database. Storing files in the database has always been controversial. However, in this case it is done to ensure that all data including the application itself can be saved using standard PostgreSQL backups. There is no need to back up the database, the application, and those files separately — everything is in the same backup. In addition, files are handled in a transparent manner which brings countless advantages if you are dealing with workflows.
Under Data & Content → Files, every uploaded file is listed with its name, MIME type, upload time, type group, and access group:
Files
Each file shows its Access Group (Public/Private). Use the Actions column to open, edit, or delete a file.
The core question is: why would anybody use this feature? What are the benefits of such infrastructure? Here are some typical use cases:
- Display images
- Offer downloads
- Send as email attachments
Once a file has been uploaded, its Group decides who is allowed to access it — Public or Private. As with all other data, permissions are handled by the database directly and are therefore identical within the entire stack (API, GUI, etc.). Click the pencil icon to change a file’s name, group, or type:
Edit File
Name, Group (Public/Private), and Type can all be changed after upload.
Inside the WYSIWYG editor the application designer can make use of such files. Developers have direct access to CYPEX storage and files can be taken from there.
Click Upload to open the upload form. The infrastructure is usually used for pictures as well as documents (PDFs, etc.) which are static in nature:
Upload Files
Set a Name, Group, and Type, then select or drop the file.
Various types of binary files are supported. The Type dropdown offers:
- Image
- Video
- Audio
- Document
- Text
- Other
- REST API — test file endpoints.
- Storage Repositories — repos used to fetch binary content.