jee-r

# See: https://emby.media/community/index.php?/topic/22889-emby-behind-a-reverse-proxy-remote-control-issue/

server {
        server_name mydomain;
        listen 80;

        rewrite ^ https://mydomain$request_uri? permanent;
}

server {

jee-r

Possible values for ext-name:
bcmath 
bz2 
calendar 
type 
curl 
dba 
dom 
enchant 
exif 

jee-r

Keybase proof

I hereby claim:

• I am flip-bs on github.
• I am flip (https://keybase.io/flip) on keybase.
• I have a public key ASArE3VUyB73eXHuD0oaMIum-nrF4CXoOKLpCg8od-nzmgo

To claim this, I am signing this object:

jee-r

#  Backup Manager Configuration File
#
#  * This configuration file is divided into sections.
#    The 'global' section is mandatory, every keys defined in 
#    this section are inherited in the other sections.
#  * There is one section per "backup method", you have to 
#    fill the section of the chosen method.
#
##############################################################

jee-r

server {
  listen                     80;
  server_name                #DOMAIN#;
  return 301 https://$server_name$request_uri;

}

server {
    listen 443 ssl http2;
    server_name #DOMAIN#;

jee-r

FROM alpine:3.19

ENV WATCH_DIR \
    BETANIN_API_KEY \
    BETANIN_API_URL

RUN apk update ; \
    apk upgrade ; \
    apk add --no-cache \
        curl \