Netbird Customized Port Setup

[ismail0234]

Describe your changes

Allows Netbird to be installed and used on different ports. The reason why this was necessary was that if you wanted to install netbird next to a web server, it was not possible. I have reorganized it with reference to the tickets below. Apart from quick setup and advanced setup, it can be used as a 3rd file in the form of quick and customized port setup.

Issue ticket number and link

#1786
#1794
#1410

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

[ismail0234]

Only 3 values are requested from the user during the setup phase.

1. HTTP PORT (default: 80):
2. HTTPS PORT (default: 443):
3. CLOUDFLARE API KEY

After entering these 3 values, the installation is automatically completed. SSL certificate assignment and renewals are completed via cloudflare api.

[ismail0234]

If you are using a database like MySQL, usually this comes alongside a web server. So people might need customized setup. #2837

[ismail0234]

The example of use is the same as for quick setup.

export NETBIRD_DOMAIN=netbird.example.com;  ./getting-started-custom-ports-with-zitadel.sh

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mlsmaycon]

@ismail0234 I think it is better for us to keep this one outside the mainstream since it may cause more Github issues, and we can assume that users who already have services running on a server might know how to customize their deployment.