Links
📃

Installation Document

🔰 Introduction
A local installation of Ellipsis Drive (ED) allows you to run ED on your own (virtual) environment. You can launch ED on top of your current file storage (whether that is S3, a classic file server or another form of cloud storage).
Deploying ED can be done independently, but we do recommend you to hire an ED consultant for at least 3 months to get it launched correctly and to guide early use.
ED can be deployed in a geographically distributed environment. That is to say, you can make your ED deployment perform even if users are distributed around the world.
🔐 Security configuration
When launching ED you can configure your preferred security settings. Here you need to consider security versus friction. Our recommendations depends on your industry and desired use.
List of things that can be configured
👈
​
​
💽
File storage
ED works as a layer on top of classic file storage (that we call passive storage). This layer takes care of access management, search, interoperability and scalability.
It is important to note that content in passive storage is not altered. ED needs read and write access to this file storage, but will not alter the files itself in any way.
If you have processes that need direct read access to files in passive storage, that is no problem. This can for example be necessary if you need extremely high read speed for some algorithms and want to bypass the API. It can also be needed if you have legacy code that you do not wish to migrate.
ED is compatible with other processes reading the files. But ED is not compatible with other processes having writing access to the storage. You will need to add files via the ED API. (Otherwise glitches in the system can occur)
💠 Components
ED consists of 11 containerized components, that should each be launched on a (virtual) server running linux Ubuntu 16 or higher. Multiple components can run on the same server, but for optimal use we recommend to install them on different servers.
List of components
👈
​
📶 Scaling
The components marked with '(pool)' can have multiple instances running. Instances can be added or removed from the system when scaling up or down.
The API and cache database can be placed on any geographic location. They do not need to be near the main location.
List of requirements and recommendations
👈
​
​
🚀
Launch
An ED consultant will be dedicated to your launch, so these steps will not have to be taken by the client alone.
List of steps to launch a component
👈
​

FAQs

​
🤔
What do I do if I have no file storage of my own?
​
🤔
Are there any features in the public ED version that will not be available in the private instance?
​
🤔
Will the ED UI be included in my private instance?
​