Files versionning allows you to keep track of file changes.
The current implementation is based on Git for the sake of simplicity, and it has some drawbacks :
- Only works for FS-based workspaces
- Git is known for not very well scaling for huge files. Thus if you are planning to use only media files for example (videos), you should probably avoid this. Appart of that, it’s working neatly, and implementing versionning through a git workspace also allows you to interact with the versionning system through external application.
Once installed, you will be able to see a list of actions of what happened on a given file, eventually download a given previous revision, or directly reverse the current revision to a previous one (thus creating a new revision). To install, simply make sure that the GIT command is accessible through the command-line on your server, and that the PEAR/VersionControl_Git client is installed as well.
Previous implementation was based on SVN instead of Git. As they share some client resources (history browser), the meta.svn plugin must be installed as well (it is by default).
Then add a “Git-based versionning” feature to the workspace.
When switching for the first time to this workspace and making a file operation (upload, move, whatever), a “git init” operation will be launched. If you encounter strange errors, maybe you can manually initiate the workspace by applying the following command line at the root of your workspace path :
$ git init .
$ git add .
$ git commit -a -m "Initial commit"
Other versionning systems should be introduced in future versions, either leveraging specific access drivers capacities (cloud storage generally directly provide versioning, accessible through an API), or by storing diffs and version in an additional database.Back to top