Jose Diaz-Gonzalez ba3ad4a9ab fix: do not allow reusing the same scheme:host-port mappings when setting ports ...

This doesn't make sense as a port can't be listened to twice on the same domain, so instead we should just fail immediately if someone attempts to perform this action.

Refs dokku/dokku-letsencrypt#269

2024-02-25 11:11:23 -05:00

..

src

chore: remove extra trailing newline

2024-02-12 21:43:45 -05:00

.gitignore

feat: use ports-clear plugn trigger to manage clearing the port map

2023-08-05 10:58:57 -04:00

functions.go

fix: do not allow reusing the same scheme:host-port mappings when setting ports

2024-02-25 11:11:23 -05:00

go.mod

chore: bump go modules

2024-02-11 02:49:00 -05:00

go.sum

chore: bump go modules

2024-02-11 02:49:00 -05:00

Makefile

refactor: only use detected port mapping if override is not specified

2023-08-05 10:58:57 -04:00

plugin.toml

Release 0.33.7

2024-02-22 18:14:04 +00:00

proxy.go

fix: do not allow reusing the same scheme:host-port mappings when setting ports

2024-02-25 11:11:23 -05:00

report.go

feat: write auto-detected port mappings during a deploy

2023-08-05 10:58:57 -04:00

subcommands.go

fix: do not allow reusing the same scheme:host-port mappings when setting ports

2024-02-25 11:11:23 -05:00

triggers.go

fix: do not allow reusing the same scheme:host-port mappings when setting ports

2024-02-25 11:11:23 -05:00