blackoverflow / dev-env-signal-server Goto Github PK

Due to #5, Profile handling is broken.

A dummy implementation is needed.

Signal Server uses AWS for Attachments and Profiles.

I don't want to need AWS for my dev env.

Broken Attachment and Profile handling are acceptable right now.

Signal Server supports Push Notifications via ACM and APN.

I'm fine with broken Push Notifications in my dev env.

I don't want to send sms for my dev environment. I don't need twillo.

This will break the account registration, since the registration pin is send by sms.
That's ok, for now.

Having a Dockerfile for this Signal Server would allow painless setup.

In order to register a new account, I need to enter a verification code.
Due to #1, the Signal Server doesn't disclose the verification code.
In dev env, it is easiest if the verification code is fixed on a magic number. e.g. "111111"

This isn't secure. But there is no need for security in dev env.

Due to #5, Sticker handling is broken.
I don't think that this needs to be fixed.

#3 and #4 break Attachment handling.

That is bad, because its needed in a development environment.

I need a dummy attachment handling, which is compatible but doesn't need amazon or google.

Signal Service uses GCP for Attachments.

I don't want to use GCP.

Broken Attachment handling is acceptable right now.

Signal Server uses CDN for Stickers.

I really can live without Stickers.
It should even only affect the feature to create new stickers.

A lot of tests break due to the pruning.
They need to be fixed or removed.