runlike VS SirTunnel

You can use this tool to figure out how to run again any currently running container https://github.com/lavie/runlike

Issue for podman support: https://github.com/lavie/runlike/issues/71

I had started out the same way, especially if it was a new app and I wasn't familiar with how I really wanted to run it. Some containers expect a fair number of environment variables and multiple mounts. Once I got everything working, I would create a script /svcs with the corresponding docker run command. There's even a cool tool called "runlike" which can create a well formatted command for any running container.

https://github.com/lavie/runlike/

But I've got those migrated to docker-compose files these days and I try to start with the docker-compose file instead of going directly into testing out docker run commands.

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.

* Great examples which provided inspiration include Cloudflare tunnel, Tailscale Funnel, SirTunnel, Localhost.run, Fractual Mosaic, Pinggy, Tunll, and of course, the original Ngrok.

All you need is a cheap VPS with decent transfer allowance (RAM and CPU doesn't matter much) and this

Personally I'd recommend setting up a one-time ssh remote tunnel on a VPS. That's essentially what SirTunnel does. If that works, try adding Caddy in front of it to get auto-HTTPS.