All about Easy Project Server

The server solution is designed for your own server (you host the software). By purchasing this solution you obtain installable software + the source code. The server solution includes three months of free updates. Updates are available for download in the client zone, to which you obtain access after the purchase. Further updates are paid.

Virtualization – VMware, VirtualBox 

The easiest way to deploy Easy Project is in our provided virtual machines preconfigured for optimal performance. VMware and VirtualBox compatible machines are provided without extra charge. For a minor fee, we can also provide a Hyper-V machine.

Easy server requirements check

Our applications are dependent on all sorts of systems, which is quite normal – we are living in an era of integrated technology. To keep the dependencies in order, we have devised a very simple tool that checks the important components on the server. The admin just runs a simple command, which results in a neat table listing the components and their status. Such information is valuable not only for the admin, but eventually also for our support staff that can provide better instructions for a fix if the customer turns to us.

Manual and guidelines

Server environment is a diverse jungle of ridiculous proportions. To keep all parts in a perfect sync requires tons of experience and continually refreshing your knowledge about new technologies. For the most crucial configurations and components related to our applications, we have published instruction manuals and guidelines that assist admins in regular server maintenance.

These include – installation manuals, ruby updating, server configurations, useful commands or common server errors, and more.

Limitations of server solution

Support flexibility

While we always try our very best to provide customers as much useful information and tools for smooth running of their self-hosted application, we cannot directly control their environment. That means we have no ability to perform fixes directly on the server, or we cannot look for the cause of various errors occurring on the server which leaves us only guessing when providing support.

Remote server support performed by our administrators is available as a paid service. Furthermore, the resolution time is always longer when compared to cloud solution – simply due to arrangements needed before access to client server can be provided. Which leads to next point:

Access restrictions and issues

In most instances when a customer asks for server support, they cannot provide direct access to the server, but rather a remote-controlling session via apps such as TeamViewer. It is better than having no access, but our experience show a significant decrease in flexibility and resolution time when using remote-controlling tools in comparison to direct (SSH) access – connection issues with the hosting computer, lagging, and loss of control when the customer uses the computer. It all adds up to 50% slower resolution time than with SSH access.

Scheduling

Demand for server admins is larger than supply that is a cold hard fact. Server support is no exception. For this simple reason, server support must be scheduled in advance, so that there is a sufficient time frame for complete resolution of the issue.

This is especially true if the only access option is via remote-controlling where the customer’s admin must be present. If the customer provided us SSH access, this problem is a bit smaller – our admin starts the repair immediately when available and doesn’t need to meet up with the customer’s admin.

Bug report verification

It not far-fetched to say that every server environment is different. With so many configuration options, you would think it is impossible to have two identical servers. This is often the reason why we cannot simulate an in-house a specific behavior described by the customer which acts as a bug.

If a service required to run our application is configured differently as our recommendation, it is not necessarily wrong, but may cause issues in the application that are hard to trace back to that configuration.