Andrew Koltsov

will it be included in cartridge, or I should patch it my self?

Got same issue: cert was generated for sandbox, solution: set `APNS_USE_SANDBOX=True`, but it may work on opposite way, if you are using production cert with `APNS_USE_SANDBOX=True`

I'm using python:3.8-slim-buster docker Image I solved it with ``` RUN echo "patching open ssl" RUN cp /etc/ssl/openssl.cnf /app/openssl.cnf RUN chmod 777 /app/openssl.cnf RUN sed -i "s/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g" /app/openssl.cnf ENV OPENSSL_CONF=/app/openssl.cnf...

is it possible to make a new release with this minor change only?

@gj at this moment with out platform specification I'm getting `ERROR: Could not find a version that satisfies the requirement oso==0.27.0 (from versions: none)` on arm mac, but with `platform:...

> @andrewkoltsov what version of golang are you using? And do you have `CGO_ENABLED=1` set when building? to be honest i don't know, I'm installing it from pypi (oso =...

with ``` ~/bin/erlc \ -o ebin \ -I include -I /home/ejabberd/lib/ejabberd-23.4.0/include \ -DLAGER -DNO_EXT_LIB \ src/*erl ``` it fails too with `init terminating in do_boot ({cannot get bootfile,no_dot_erlang.boot})`

@licaon-kter actually I did a minor modification: add trailing slash to make it work with my rest api

I made it compile with ``` FROM ejabberd/ecs:23.04 USER root RUN set -xe \ && apk add --update --no-cache --virtual .build-deps \ build-base \ erlang-dev \ git \ mc USER...

thank you, actually I'm running ejabberd in k8s, and I'm not sure that CTL_ON_CREATE approach will work, because I'm expecting to have an image with everything installed and ready ejabberd.yml