Support custom public address in generated configurations

[guzalv]

Fixes #1

[guzalv]

I started with adding URL parameters for public IP/port, and I have my first questions

Should we add a parameter for each of IP and port, or 1 for the whole address, including IP and port? Having 2 parameters is simpler (no need for string manipulation, edge cases). Having just 1 seems simpler from the user's perspective.

A related question is whether it makes sense to customize only one of address and port. Perhaps even if we use 2 different parameters, it should be enforced that both are present?

Update: removed port handling, I realized it's unrelated from this feature.

[coveralls]

Pull Request Test Coverage Report for Build 12931715286

Details

• 0 of 4 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.4%) to 9.677%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
main.go	0	4	0.0%

Totals
Change from base Build 12599671838:	-0.4%
Covered Lines:	9
Relevant Lines:	93

---

💛 - Coveralls

[rg0now]

We're almost there, only minor stuff missing. Once ready please try to repack the whole thing into a single commit so that we can simply git-merge and still get a clean history. Thx!!!

[guzalv]

We're almost there, only minor stuff missing. Once ready please try to repack the whole thing into a single commit so that we can simply git-merge and still get a clean history. Thx!!!

I have now made fixes and squashed all commits into one. Thanks for your comments!

[rg0now]

Sorry for the nitpicking again. I promise this is the last time. Let me know if you're fed up with this and want me to jump in and to the renamings all over the place

[guzalv]

Thanks, and no worries at all! I should have done this by myself after you recommended to change the env variable. I have made the fixes, let's see how it looks now and still correct what's necessary.

[rg0now]

Thanks a lot, applied!