Oct 3, 2014 at 3:11 PM
Edited Oct 3, 2014 at 3:13 PM
There is a new branch called attachments that does some refactoring to how attachments work.
- Configuration of storage type (database vs filesystem) is now at the application level instead of project level
- Attachments can be disabled / enabled at the app level, and the project level.
- Upload path can now be absolute C:\whatever or relative ~\Uploads.
- Project upload path is set to a GUID by default when creating or cloning a project and cannot be changed
Migration poses an interesting challenge for users that have mixed filesystem and database attachments project by project. If you have set all your projects to database or filesystem, then migration should be super easy.
If you can, let us know if you fall into this situation where you have mixed storage types by project. Worst case I think we can whip up a console utility to move file system attachments into the database and vice versa.