rm horizon container — app seems to expect to see the horizon process

Horizon

Add horizon service

Run another container for Horizon - Let's try something simpler than for Sentry containers.

Put again the queue in sync mode — redis silently fails

Use app:app uid/gid. Okay we've a redis container, so let's use it? Configure session cookie.

As we switch from Pixelfed's contrib/ version to our version,
we need to update the path.

Fix mailgun credential key

Configure mail (Mailgun, SMTP)

Set HTTPS to 1, as HTTP_X_FORWARDED_PROTO is ignored.

Why only Dwellers? We're going to deploy a k8s next.

Fix whitespace issues

Remove Makefile (npm only)

Switch to nasqueron/pixelfed image

Notifications center can again connects to the broker.

For reference, upstream Docker image uses the following PHP configuration:

Fix indent. vpx → webp

Per http://svn.php.net/viewvc/phpdoc/en/trunk/reference/image/configure.xml?view=markup&pathrev=339664 library has been changed: instead to use libvpx has been superseded by libwebp.

imagefttext() and imagecreatefromxpm() ok

GD requires additional support for freetype, xpm and webp (vpx)

Set REDIS_PORT

Configure max number of photos per post, proxy IP

Generate app_key. Configure domain, title, log, mail.

Redis container deployed.

Next step : provision application key

Set image

proxy_params

WIP

• /srv/redis/pixelfed_redis created
• pixelfed_redis container is running

Give SaaS Sentry pillar entries to Dwellers. Parse project id as string.