Seafile is a self-hosted online file storage system. The features are comparable with Dropbox, but it can be installed locally and sync inside the LAN or to a self-hosted root server. It features sync, webdav and online access. Check out the feature matrix for more.

The Seafile deployment works straight forward and requires you to have access to your-server-ip:8000 and :8082. There are two problems with this solution:

- Port 8000 and 8082 must be reachable from outside world and the client must be able to connect to it. This can easily become an uncontrollable obstacle once you want to connect through a firewall or proxy that blocks those ports (common in companies). - The data transport is not encrypted between the client an the server, which makes it easy to spy on data and passwords when logging on to the web-interface for example.

To overcome this issues, it is common practice to configure a webserver as a reverse proxy. The webserver will establish a secure connection to the client and internally forwards the request to Seafile.

The documentation describes how to deploy Seafile under an NGINX and APACHE webserver.

I'm using lighttpd, which is not listed.

→

2017/07/17 10:43 · sdk

This document describes the basic development and deployment life-cycle for SAP Cloud for Customer custom development using the SAP Cloud Applications Studio. The SAP Cloud Applications Studio is a client application installed on the developer's computer and connects using a secure SSL connection to the SAP Cloud for Customer System. One physical system can host multiple Cloud for Customer tenants. A tenant is an secure and isolated run-time with one URL. Using this technique, SAP is capable of hosting multiple SAP Cloud for Customer instances for one or more customers on one system.

The SAP Cloud Application Studio gives the developer an easy development environment where he can develop event and script based without knowing the system internal architecture.

All entities created with SAP Cloud Applications Studio are stored in the common area of the system. They are invisible for all customers but the customer for which the solution has been developed. Only this customer can activate the solution in his tenants. There is a recommended way to set up a system landscape that includes custom development.

→

2017/07/14 13:14 · sdk