Zotlabs|Hubzilla Development

Andrew

Fri, 09 Nov 2018 12:52:48 +0000

I finally succeeded in deploying a hub using Traefik and docker-compose. Traefik acts as a reverse proxy and automatically obtains and installs LetsEncrypt SSL certificates for you. Ideally this will allow people to deploy a hub with almost a single command. It would allow the Hubzilla developers to maintain the system dependencies and things like database optimizations. There are still some things to work out, including the cron job and the DNS issue with the database container address (merge request submitted).

show all 9 Comments

mrjive

Fri, 09 Nov 2018 13:57:21 +0000 last edited: Sat, 10 Nov 2018 14:15:43 +0000

Actually I was wondering where were you... Now I know the answer

BOET

Fri, 09 Nov 2018 20:46:10 +0000

Phewww... I believe this can be BIG!

Herbert Thielen

Fri, 09 Nov 2018 21:08:17 +0000

Sounds great!

Anmol Sharma

Fri, 09 Nov 2018 23:37:08 +0000

Hello,

For the followers of #docker, here are 3 new #Yunohost 3.2 images for AMD64, I386 ARM from #domainelibre: #Hubzilla , #osada #zap can be installed on Yunohost with #LDAP support which have #LetsEncrypt too.

https://hub.docker.com/r/domainelibre/yunohost3/

https://hub.docker.com/r/domainelibre/yunohost3-i386/

https://hub.docker.com/r/domainelibre/yunohost3-arm/

Have a good day !

Andrew

Sat, 10 Nov 2018 00:53:47 +0000

Thanks for the links. I didn't know YunoHost had Docker deployment now. It is a bit surprising, since YunoHost is itself serving a similar purpose to Docker. It's not a perfect analogy, obviously, but I think of YunoHost more like a Linux distro that you run in order to make installing and maintaining self-hosted web services easy through a web browser GUI. Software is infinitely permutable I suppose. If it makes things better for some people, I'm glad there is the option.

One thing I like about this docker-compose approach using Traefik is that it is straightforward to run the Hubzilla container and its coupled database container without the Traefik reverse proxy if you want to handle the web server component some other way. It's trivial to maintain two deployment methods this way since they are so closely related, and it provides more options for hub operators who have different needs.

Anmol Sharma

Sat, 10 Nov 2018 02:26:15 +0000

I get your point:

YunoHost is itself serving a similar purpose to Docker

There is an app to run #docker inside #yunohost . And another app which runs #yunohost inside #yunohost but I don't know what purpose it Serve. #Docker is really nice to run apps as it has become a web app deployment standard and every app gives/aims to provide support for #docker.

Andrew

Tue, 13 Nov 2018 20:35:07 +0000

Still working on this thing. The primary challenge is the fact that we have these DNS checks that fail from the docker container for some reason, but I can't bypass them using the existing Hubzilla config settings because those can only be added to .htconfig.php prior to database creation. But, if .htconfig.php exists, the hub setup is skipped because it assumes the database has been installed. My solution is to hack around this by installing the database schema via shell script when the container is initally started (if it does not already exist), and to generate the .htconfig.php in the Dockerfile, substituting or generating the relevant info. This should allow the admin to just immediately to the registration step based on the admin email they specified in the docker-compose parameters.

Tue, 13 Nov 2018 22:34:28 +0000

This is why there is .htpreconfig.php

Andrew

Wed, 14 Nov 2018 11:40:25 +0000

That doesn't help the DNS check that fails when you do the admin account registration. At that point, the database has been installed and a new .htconfig.php generated. The only way you can add the config to disable DNS check after the web-based setup process is by modifying the Hubzilla code which I didn't want to do.