TALER-MERCHANT-RPROXY-SETUP(1)

πŸ“¦ version 1.3.0, in nixos 26.05, nixpkgs unstable

πŸ’… taler-merchant-rproxy-setup(1) β€” GNU Taler core manual vibes ✨

okay so bestie, picture this: you've got a Taler merchant backend just sitting there, and now you need a reverse proxy in front of it. this page is your girl. it's taler-merchant-rproxy-setup(1), part of the GNU Taler fam, and honestly? it's giving "glow-up for your infrastructure" πŸ¦‹


🌸 NAME 🌸

taler-merchant-rproxy-setup β€” the little tool that sets up the reverse proxy for a Taler merchant backend for you, automatically, no cap ✨


πŸŽ€ SYNOPSIS πŸŽ€

taler-merchant-rproxy-setup [--domain=NAME] [--nginx | --apache]
                            [--httponly | --httpsonly] [-h | --help]

πŸ’– DESCRIPTION πŸ’–

so taler-merchant-rproxy-setup is a command-line tool that configures a reverse proxy for the Taler merchant under either the Nginx or the Apache HTTP server. chef's kiss. πŸ‘‘

it can also optionally enable HTTPS via certbot β€” unless you specifically ask for --httponly, in which case it stays cute and plain over HTTP.

if you don't say --nginx and you don't say --apache, the script does a lil vibe check: it looks at whether exactly one of them is installed and just goes with that. if neither is installed, or (iconic disaster) both are installed, it exits with an error. like, pick a lane babe 😭

the script updates the default reverse-proxy configuration file β€” that's /etc/nginx/sites-available/taler-merchant for Nginx, and /etc/apache2/sites-available/taler-merchant.conf for Apache β€” and backs up any existing version to a .legacy suffix. we love a backup, self-care era 🫢

if HTTPS is enabled (which is the default unless you pass --httponly), certbot is run to obtain TLS certificates for the configured domain name, and the config gets adjusted accordingly. and if you ask for --httpsonly, then HTTP requests get redirected to HTTPS (port 443). finally, the script activates the new site configuration and reloads the respective web server. slay, deployed. πŸ”₯

to make sure the configuration actually succeeds, both the web server (Nginx or Apache) and certbot (unless --httponly) must be installed. and in the case of Apache, some modules (proxy, proxy_http, headers) must be enabled β€” yes bestie, all three, no skipping. the script checks for these prerequisites and exits with an error if any are missing. it's not mean, it's just looking out for you πŸ’€


✨ OPTIONS ✨

  • --domain=NAME β€” Required. the fully qualified domain name (FQDN) you're setting the reverse proxy up for. not optional, bestie, this one's mandatory πŸ’…
  • --nginx β€” forces Nginx as the reverse proxy. if you don't specify it, the script auto-detects whether Nginx or Apache is installed β€” but only works if exactly one is installed.
  • --apache β€” forces Apache as the reverse proxy. same deal: if you don't specify it, the script auto-detects whether Nginx or Apache is installed, provided exactly one is installed.
  • --httponly β€” only configure HTTP, no TLS. skips certbot entirely and omits all TLS-related configuration. incompatible with --httpsonly 🚫
  • --httpsonly β€” configures HTTPS and automatically redirects HTTP traffic to the HTTPS port. incompatible with --httponly 🚫
  • -h, --help β€” prints short help on options. tiny, helpful, adorable.

πŸ¦‹ SEE ALSO πŸ¦‹


πŸ’€ BUGS πŸ’€

found a bug? don't suffer in silence, report it! use https://bugs.taler.net/ or send electronic mail to <taler@gnu.org>. the devs genuinely wanna hear it πŸ“


πŸ‘‘ AUTHOR πŸ‘‘

GNU Taler contributors β€” a whole squad, fr fr πŸ’œ


2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)


okay that's the whole page, you're literally a reverse proxy expert now 🧚 version 1.0, dated Dec 22, 2025 β€” go forth and configure, bestie, and may your certs never expire on you πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from