Load configuration from URL rather than local file about uniqush-push HOT 6 OPEN

This is a good point! Let me see if I can make this change in next week. It should not be very hard.

from uniqush-push.

Hm, I don't see why not. 👍 for the idea

from uniqush-push.

@tleyden I bet then it would also be nice for you to have APNS pems stored inside Redis instead of on the file system?

from uniqush-push.

@mishan just curious, would that be for security reasons or ease of use?

from uniqush-push.

Ease of use -- I haven't found it totally convenient to host it on the filesystem either. It's not ideal to store blobs of data in Redis but it's small and there shouldn't be too much of it that it should be OK. The Redis best practice is indeed to store the path as it is doing now.

from uniqush-push.

It's easy to do, but there's other ways to accomplish this, and not sure if this is a common use case.

An alternative is to use a volume to add a folder with the certificates, or files with the certificates.

curl http://path/to/remote/uniqush-push.conf -o ~/path/to/uniqush-push.conf || exit 1 (or equivalent) could be used as another alternative in a startup script wrapping uniqush-push, so it seems unnecessary to include it (other services, such as redis, memcached, etc. don't generally download configs from a URL, to my knowledge).

https://docs.docker.com/engine/admin/volumes/volumes/#choose-the--v-or-mount-flag

Also,

I bet then it would also be nice for you to have APNS pems stored inside Redis instead of on the file system?

#123 would have to be solved first.

from uniqush-push.