Well, Stash works just like the other Atlassian applications, so you can do what @Larry Shatzer suggested and reverse-proxy it to another webcontainer listening on port 80 OR you could change the server.xml for Stash's Tomcat to listen on port 80.
This isn't as much a Stash question as it is a web-container/application question, good question though.
You can change server.xml. Also make sure to start the application under superuser otherwise sometimes you will not be able to bind to dedicated ports like 80 without root privilege.
So, you're able to change the port to 80? Could mark this as the answer? And just a heads up, the server.xml file did move recently so that you wouldn't have to carry over customizations when you upgraded. Old location: <Stash installation directory>/conf/server.xml New location: <Stash home directory>/shared/server.xml
You can't change the port to be port 80 if you're running linux. In order for a process to be run on a port <100 it needs to be run as root. I would not run Stash as root because of the git hooks.
To "change" the port - add nginx or apache in front of it and have them reverese proxy to port 80. You can do it with iptables as well but that might get messy real quick.
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