Mastodawn

varaki Jul 19, 2023

Bromite's fork is going to be branded as Cromite

Bromite's fork is going to be branded as Cromite - Lemmy.world

cross-posted from: https://lemmy.world/post/1766078 [https://lemmy.world/post/1766078] > Bromite’s actively maintained fork is going to have its own branding starting from next release according to the latest release notes [https://github.com/uazo/bromite-buildtools/releases/tag/v115.0.5790.98-30d36db90516e651c2cd676a677268b3ea7cf75b]: > > >>Please note: this is the last release, the next one will be in https://github.com/uazo/cromite [https://github.com/uazo/cromite]

varaki Jul 19, 2023

Bromite's fork is going to be branded as Cromite

https://lemmy.world/post/1766086

Bromite's fork is going to be branded as Cromite - Lemmy.world

varaki Jul 19, 2023

Bromite's fork is going to be branded as Cromite

https://lemmy.world/post/1766078

Bromite's fork is going to be branded as Cromite - Lemmy.world

Bromite’s actively maintained fork is going to have its own branding starting from next release according to the latest release notes [https://github.com/uazo/bromite-buildtools/releases/tag/v115.0.5790.98-30d36db90516e651c2cd676a677268b3ea7cf75b]: >>Please note: this is the last release, the next one will be in https://github.com/uazo/cromite [https://github.com/uazo/cromite]

varaki Jul 6, 2023

immich nginx configuration

https://lemmy.world/post/1100746

immich nginx configuration - Lemmy.world

cross-posted from: https://lemmy.world/post/1100232 [https://lemmy.world/post/1100232] > - I tried to bring up an immich [https://github.com/immich-app/immich] server on a cloud provider server with docker, which is successful, but I’d like to organize multiple services into locations under the top level domain, which is a duckdns.org [http://duckdns.org] domain with nginx reverse proxy. > - So I’d like to reach immich under “https://something.duckdns.org/immich/ [https://something.duckdns.org/immich/]”, but I can’t seem to make it work, because if I load it, it redirects me to “https://something.duckdns.org/auth/login [https://something.duckdns.org/auth/login]” (so it uses the top level, not relative to the /immich location) > - If I manually change it to “https://something.duckdns.org/immich/auth/login [https://something.duckdns.org/immich/auth/login]” the page loads, but it shows an error message “Unable to connect” > - If I put it under the / location, it works, but I don’t want that > > - Do I need to change something in the docker compose yaml or the .env files to make it work? > - Or is my nginx config messed up? > - On my home server I was able to successfuly set up multiple services in a similar way, I just can’t make it work with immich-app. > > Does anyone has any idea? > > Here is my nginx configuration: > > server { > listen 80 default_server; > listen [::]:80 default_server; > > listen 443 ssl default_server; > listen [::]:443 ssl default_server; > ssl_certificate /etc/letsencrypt/live/MYDUCKDNS_DOMAIN_GOES_HERE/fullchain.pem; # managed by Certbot > ssl_certificate_key /etc/letsencrypt/live/MYDUCKDNS_DOMAIN_GOES_HERE/privkey.pem; # managed by Certbot > > root /var/www/html; > > index index.html index.htm index.nginx-debian.html; > > server_name _; > > location / { > try_files $uri $uri/ =404; > } > > location /immich/ { > proxy_pass http://localhost:2283/; > include proxy_params; > > proxy_http_version 1.1; > proxy_set_header Upgrade $http_upgrade; > proxy_set_header Connection "upgrade"; > proxy_redirect off; > } > } >

varaki Jul 6, 2023

immich nginx configuration

https://lemmy.world/post/1100232

immich nginx configuration - Lemmy.world

- I tried to bring up an immich [https://github.com/immich-app/immich] server on a cloud provider server with docker, which is successful, but I’d like to organize multiple services into locations under the top level domain, which is a duckdns.org [http://duckdns.org] domain with nginx reverse proxy. - So I’d like to reach immich under “https://something.duckdns.org/immich/ [https://something.duckdns.org/immich/]”, but I can’t seem to make it work, because if I load it, it redirects me to “https://something.duckdns.org/auth/login [https://something.duckdns.org/auth/login]” (so it uses the top level, not relative to the /immich location) - If I manually change it to “https://something.duckdns.org/**immich**/auth/login [https://something.duckdns.org/**immich**/auth/login]” the page loads, but it shows an error message “Unable to connect” - If I put it under the / location, it works, but I don’t want that - Do I need to change something in the docker compose yaml or the .env files to make it work? - Or is my nginx config messed up? - On my home server I was able to successfuly set up multiple services in a similar way, I just can’t make it work with immich-app. Does anyone has any idea? Here is my nginx configuration: server { listen 80 default_server; listen [::]:80 default_server; listen 443 ssl default_server; listen [::]:443 ssl default_server; ssl_certificate /etc/letsencrypt/live/MYDUCKDNS_DOMAIN_GOES_HERE/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/MYDUCKDNS_DOMAIN_GOES_HERE/privkey.pem; # managed by Certbot root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name _; location / { try_files $uri $uri/ =404; } location /immich/ { proxy_pass http://localhost:2283/; include proxy_params; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_redirect off; } }