Docker KoBo Toolbox running behind reverse-proxy with SSL support

User Support
#1

This is an update to the original post on this subject located here.

A stream lined method of deployment curated on github has been placed here. The deployment consists of three parts:

  1. Docker server setup,
  2. Reverse-proxy deployment and network configuration/testing,
  3. KoBo Toolbox deployment.

All the instructions necessary to deploy KoBo Toolbox behind jwilder reverse-proxy with automated letsencryp SSL support are included in the github readme files.

Note: kobo-docker-ripcord lags behind kobo-docker development. Latest and greatest KoBo features may not be available until compatibility issues between Kobo and the reverse-proxy are resolved.

Professional deployment assistance is available through Ripcord Engineering. Cost to deploy depends on the particular deployment environment and the client. Pro bono work is available for qualifying charitable organizations.

Regards,
Jake Staub

#2

Click here for a link to a deployment wiki that gives two self-deploy KoBo Toolbox options.

Regards,
Jake

#3

After helping two parties deploy KoBo Toolbox I highly recommend deploying via Amazon Web Services (AWS). Over a month was spent attempting to make self hosted web accessible KoBo instances function correctly. Fully functional AWS instances were set up in a matter of hours.

Regards,
Jake

#4

Yes I am one of those who test in AWS and is fully functional, now deploying in my production environment.

Regards,

Kaleem

ยทยทยท

On Monday, September 4, 2017 at 5:59:40 PM UTC+5, jpstaub wrote:

After helping two parties deploy KoBo Toolbox I highly recommend deploying via Amazon Web Services (AWS). Over a month was spent attempting to make self hosted web accessible KoBo instances function correctly. Fully functional AWS instances were set up in a matter of hours.

Regards,
Jake