nginx-proxy VS gotenberg

I wanted to share with you an exciting new tool that simplifies the process of interacting with the NGINX Proxy Manager API. It's a TypeScript tool that generates API requests based on environment variables within a Docker container. This tool is heavy influenced by the https://github.com/nginx-proxy/nginx-proxy but it works with npm.

I use an automatically configuring reverse proxy - there's several to choose from, but the nginx-docker image is really nice, and comes with another image to do automatic SSL with certbot (if you wanted to host things externally).

Docker runs on the 3B+ so you could use this [Github] or the one I have deployed here [NGINX Proxy Manager site] amongst others.

setting up letsencrypt with nginx-proxy and acme-companion

Here is the link, sorry😅

Shit... Here is the link: https://github.com/nginx-proxy/nginx-proxy

I use the nginx-proxy image and it's acme companion image for automated reverse proxy configuration and certbot.

I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).

https://github.com/nginx-proxy/nginx-proxy for reverse proxy

I currently use this (https://github.com/nginx-proxy/nginx-proxy) and I was able to configure anything via env vars. Some minor nginx include files were needed tho. But no UI. So far I was stunned that it works so well. Deploy a new container add 2 env vars. Done. With automated SSL.

Otherwise, any pdf to hml chromium based solution hosted via docker, like gotenberg](https://github.com/gotenberg/gotenberg) or browserless.io(which is free if you create open source). Generating pdfs from html directly in .NET was always a pain. Wkhtml (and wrappers that use it) uses WebKit and comes with a load of issues of its own, similar to running and styling anything in Safari. Using chromium based engine saves a lot of time as it's the most popular way of doing it these days. You can also use puppeteer-sharp with local chromium if you host your app on something that allows it(f.e. not Azure Functions).

Think you mean https://gotenberg.dev ?

We use https://gotenberg.dev/ with handlebars templates.

Yeah headless chrome is a chore, but probably the best best. We use https://gotenberg.dev in a docker container. It needs to be beefed up from time to time, but it works well

I asked the very same question a few months ago and someone suggested https://gotenberg.dev/. We've been using it ever since with absolutely no issues.

https://github.com/gotenberg/gotenberg Turns thinks into pdf.

https://gotenberg.dev/ https://github.com/ChangemakerStudios/GotenbergSharpApiClient

This looks great. I am glad to still see good work being done in this space. Interested to see how it compares to that and the other options being floated at the time like Puppet.

I had used https://gotenberg.dev/ on AWS in the past. Many of the options available at the time weren't usable in Azure outside of a VM due to needing to make use of GDI interfaces that were disabled for security reasons.