![]() PUSH_HTTPS_BIND_ADDR - Bind IP address of the HTTP endpoint.Below there's a full list of the variables you may set while running docker (via docker -e switch), but if there's something you feel, you need to change other then that, then you need to prepare your own config/prod.exs before image build.Įnvironmental variables to configure production release: Settings for HTTP endpoint: All useful options may be overridden via system environmental variables. The docker image of MongoosePush contains common, basic configuration that is generated from config/prod.exs. ![]() It contains a VOLUME for path /opt/app - it is handy for injecting APNS and HTTP API certificates since by default the docker image comes with test, self-signed certificates. The docker image that you have just built, exposes the port 8443 for the HTTP API of MongoosePush. You may run it by typing: docker run -it -rm mongoose_push:release foreground ![]() it -rm mongooseim/mongoose-push:latest Buildingīuilding docker is really easy, just type: MIX_ENV=prod mix do deps.get, v, docker.build, docker.releaseĪs a result of this command you get access to mongoose_push:release docker image. e PUSH_HTTPS_KEYFILE="/opt/app/priv/ssl/rest_key.pem" \ e PUSH_HTTPS_CERTFILE="/opt/app/priv/ssl/rest_cert.pem" \ Go to your project -> Project Settings -> Service accounts -> Generate new private keyĪssuming that you have the priv directory with all ceriticates and fcm token in current directory, then you may start MongoosePush with the following command: docker run -v `pwd`/priv:/opt/app/priv \ ![]() To see how to obtain token and key_id read:įCM JSON file can be generated by Firebase console ( ). If you want to use APNS token authentication you need to provide token and set key_id and team_id environmental variables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |