Menu
▾
▴
Home
Welcome to the eoss-edrive wiki!
We will keep this wiki updated with answers to questions as well as configurations for common use cases.
In response to one review. It was absolutely intended that the files on the file system were marked Read Only, this was by design.
However, we reworked this functionality in the 0.2.0 release and made it a bit smarted.
It will now ONLY set files on the File System to ReadOnly if you use the Command server checkin or cancel-checkout commands. As well as these 2 commands, the only other time eDrive will create ReadOnly copies on your File System is when eDrive creates, or updates, files on your File System that are versionable in your Repository. The correct way to modify these files should be to check them out first which would set the files as writable. However, if you change the Writable status of these files on your File System, eDrive should leave the permissions alone until Repository changes are re-synchronised to the File System.
Since eDrive 0.2.1 eDrive now supports the https scheme. There is a new setting that can be used in the JSON Configuration file "acceptAllCerts" that when set to true will allow you to connect via https even if you have not imported your server certificates to your client keystore. The proper way to support https is to correctly import your server certificates into your keystore and use the Java System properties to point at the correct information.
We would like to point out to users that the 0.1.x/0.2.x branches are deliberately released in "Beta" status, not because they do not work, but rather that we feel without proper security it cannot be considered to be an Enterprise or production ready product.
Please read the roadmap.txt file deployed with eDrive to see what we are working on for future releases, and if you would like to help out, or have any feature requests, suggestions, logic issues, bug reports or code to donate, please feel free to jump on board.
Regards
The EOSSOnline eDrive team.
