schklom
schklom
@BarnardCollier I tried building your Dockerfile via GitHub Actions, and it consistently bugs at the line `COPY pialert /opt/pialert` ``` #5 [1/7] FROM docker.io/library/debian@sha256:2906804d2a64e8a13a434a1a127fe3f6a28bf7cf3696be4223b06276f32f1f2d #5 resolve docker.io/library/debian@sha256:2906804d2a64e8a13a434a1a127fe3f6a28bf7cf3696be4223b06276f32f1f2d done #5 sha256:fd92fbcda272f5935dcd0dfea445cba0152208f83c8fc8d2cb74c85379145c42...
FYI, it seems that ```yaml "traefik.http.middlewares.onlyoffice-headers.headers.accesscontrolalloworiginlist=*", ``` is not needed, only setting `X-Forwarded-Proto` is required :P
Here is a way to make a repository release the apk in a GitHub Action. The code to release an apk is not very complicated, one can make a pull...
An alternative is to not define the volume (in docker-compose.yml) to store the downloaded files. Then, I update my container images via a cronjob with ```bash docker compose down docker...
@arsaboo Would you upload them when you have some time?
Why not use a different port, like `-p 80:5000`? This does not seem like a rare edge case where you need container port 80.
Oh, I didn't know that. Unless the dev fixes this, you could link snippet-box to a reverse-proxy and expose the reverse-proxy's port. A basic nginx config would do.
@codesterd I don't think that is enough. The software needs to listen on that port. Also, you don't need to build the Dockerfile if all you change is EXPOSE, this...
This sounds like a job for a reverse-proxy.
AFAIK, freezing is defined here https://github.com/PeterCxy/Shelter/blob/5c7e4b3b267f7be594f083c271d1b6cf36903418/app/src/main/java/net/typeblog/shelter/services/ShelterService.java using the library on line 8 ```java import android.app.admin.DevicePolicyManager; ``` the variable on line 33 ```java private DevicePolicyManager mPolicyManager = null; ``` the un/freeze...