We're using Bitbucket and need to remap from TCP/7999 to TCP/22. We're using Bitbucket in a Docker setup (https://bitbucket.org/atlassian/docker-atlassian-bitbucket-server/src)
I've found a documentation paper that describes how to do this for native installations:
Since this instructions describe a very work intensive way in how to do this with a proxy I'm wondering if remapping to port TCP/22 using docker configuration - mapping "-p 22:7999" or is there anything which might be problematic for production environments.
edit 2016-10-24_1500 Changing the port would possibly work, but does not update the port on all links provided by bitbucket. Bitbucket itself allows only ports above 1024.....
The documentation presents an option. However, the idea that you explained wouldn't be a problem. Any other port redirection that you're able to set up will do.
Just observe that the SSH daemon runs on servers by default on port 22 so you will need to do some extra configuration as indicated on the doc you linked (i.e. "configure multiple network interfaces on the physical machine and force the default ssh daemon to listen on all but the interface for accessing Bitbucket Server")
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot