Page MenuHomeDevCentral

Deploy Pixelfed HTTP container to Equatower
ClosedPublic

Authored by dereckson on Nov 13 2018, 00:45.
Tags
None
Referenced Files
F2749217: D2016.id5090.diff
Fri, Mar 29, 12:42
F2749016: D2016.id5113.diff
Fri, Mar 29, 11:45
F2747652: D2016.id5114.diff
Fri, Mar 29, 06:34
F2747625: D2016.id5119.diff
Fri, Mar 29, 06:28
F2745483: D2016.id5091.diff
Thu, Mar 28, 23:14
F2745230: D2016.id5089.diff
Thu, Mar 28, 22:16
Unknown Object (File)
Thu, Mar 28, 10:15
Unknown Object (File)
Thu, Mar 28, 05:39
Subscribers
None

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Passed
Unit
No Test Coverage
Branch
pixelfed (branched from master)
Build Status
Buildable 3156
Build 3404: arc lint + arc unit

Event Timeline

dereckson created this revision.

Next step : provision application key

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

Configure max number of photos per post, proxy IP

Switch to nasqueron/pixelfed image

dereckson retitled this revision from Deploy Pixelfed to Deploy Pixelfed HTTP container to Equatower.Nov 13 2018, 21:16

Set HTTPS to 1, as HTTP_X_FORWARDED_PROTO is ignored.

Configure mail (Mailgun, SMTP)

Fix mailgun credential key

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

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

Put again the queue in sync mode — redis silently fails

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

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

This revision is now accepted and ready to land.Nov 14 2018, 23:32
This revision was automatically updated to reflect the committed changes.