This guide will cover all the things you need to prepare in order for us to install the RushFiles server software. We have tried to make the preparations for installing the software as easy as possible.
Please read this guide before you start your preparations, so you get the setup that will suit your future needs.
When all the preparations are done, we will do the installation and configuration of the RushFiles server software, and also do a complete checkup of the entire solution.
Before the RushFiles server software installation can start please ensure you have gone through all the preparation steps below:
Step 1: Server requirements
The minimum server requirements are:
- Processor - 4 core QEMU Virtual CPU 2.00 GHz
- Memory - 8 GB RAM for frontend/backend servers / 16 GB for database servers
- Disk - 50 GB
- Storage capacity – Depending on your needs. Note: Your storage system needs to be attached to the IIS webserver(-s)
- Operating system - Windows Server 2012 R2 / Ubuntu 14.0.4 LTS (Linux is only for the database server)
Note: File cache disk space can be added inflight as extension of virtual drives or adding more drives to the file cache server.
Server configuration examples:
Standard Server Solution ( < 2000 users ):
Extended/High Availability Server Solution ( < 10000 users):
- apm (shareapplicationmonitor)
Back end (we recommend Linux for the server containing the database ):
Note: Physical vs. Virtual servers
RushFiles works equally well on virtual as on physical servers, it’s basically up to you how you want to setup your environment.
Of course using virtual servers will make it faster to scale the system to fit future customers’ needs and reduce the need for HA server infrastructure.
The reason for this is that the servers are installed with static data (data do not change) so saving an image after the install, and in case of a break down, just spin up a new instance of the virtual server image and system will recover. Only the file cache and the database is dynamic. The file cache saves the files on disks that would have RAID or other protection and the database is a MongoDB database that can be configured as HA and replicated to your needs (separate project) the standard installation puts the MongoDB on the domain server.
Step 2: DNS Name Setup
You have to create a DNS name for the given server and it has to be configured to be accessible from the outside.
Please note: The solution both uses [yourdomain.com] and [*.yourdomain.com]. This means that you can't use an existing web URL from i.e. [yourcompany.com]
The RushFiles solution uses a number of specific subdomains for internal system services and specific websites for creating Accounts (Customers), Shares and Users.
For the solution to work, subdomains are therefore needed. We recommend that you create a wildcard subdomain on the domain you wish to use.
If you are using NAT and your server have a private IP address, then please make sure that the DNS is translated for the internal network also, as the services are talking to each other.
This can be done in the host file on the server.
You need to open up and accept send and receive calls from all *.rushfiles.com (subdomains)
- filecache01 – outside access
- clientgateway – outside access
- companyapi – outside access
- apm (overview application monitor)
- resellerapi – outside access
- preview - outside access
- company – outside access
- webclient - outside access
- reseller - outside access
Step 3: Firewall configuration
Both TCP port 80 and 443 has to be opened in the firewall for both internal and external IPs. Any --> Your server TCP 80 + 443
Step 4: SSL certificate
The RushFiles solution requires an SSL certificate on the server(s) to work.
Purchase a *. certificate (wildcard certificate), there can be several servers added on an ongoing basis (scaling), so it's important not to have a "named server certificate".
The SSL certificate is used to encrypt the data traffic between the servers and the clients. Therefor you don't need an EV certificate for this. We recommend using 2048-bit encryption.
If you don’t have a SSL provider, we can recommend The SSL store. https://www.thesslstore.eu/rapidssl/rapidssl-wildcard.aspx or we can purchase it for you at a price of 150€.
Step 5: Conclusion
You should consider which of the decribed server configurations you need initially in order to service the number of customers and users you expect on this solution.
If you have a customer who wan't to have the RushFiles server running on their own infrastructure, that is a possibility too, and for that you also need to choose from the server
configurations mentioned in this article. This customer will then be a sub-reseller to you in your reseller portal.
Each user is able to connect to different domains from the same client, thereby not being aware directly where files are stored.
Before starting the installation of the RushFiles server software, there are a couple of things you should have at hand, let's summarize:
- You must have acquired a trusted SSL certificate before installation, otherwise the servers will not be able to
- You must have your desired DNS ready. The details about settings up DNS names is specified in the server
setup guide, you should also have received.
- You must have installed Windows Server 2012 or Windows Server 2012 R2 on your machine, otherwise the
installation program will not run.
Please contact us for planning the installation by phone or email to firstname.lastname@example.org
Please create a ticket at http://helpdesk.rushfiles.com/support/home