Hello,
We have one dedicated server for Atlassian products.
It runs Windows server.
We want to have internal domain for each Atlassian product.(like: bitbucket.local, confluence.local)
And products running on 80 port, not 8090.
Are there any solutions for this? I only could find this: https://confluence.atlassian.com/display/CONFKB/How+to+setup+Confluence+with+IIS but will this be a solution?
P.S.
Well, we just want to move from TFS to actual working tools. We have HUGE virtual stack with almost no limits in resources (2TB ram).
Anyway, we did install on one machine. You could really improve integration between your products. And different configuration on each product(exmp.: LDAP) does not look nice for company like yours.
Would be nice, if you had one installer where you could just enter your account of atlassian.com and then select what to install on what database and so on. With integrations out of the box. It takes a lot of time to configure your products.
Running several Atlassian applications on a single server is fine, as long as you take into account
Because of those points, most people will generally not want to run them all on the same box. But it does work - the applications are not an issue, it's the co-hosting and resourcing implications.
Your other problem about the ports is a case of getting proxying right. You still run the applications on port 8080, 8085 and 8090 etc, but within IIS, you need to tell it "when listening on domain jira.local:80, proxy the connections through to localhost:8090". The document you've found covers doing that for Confluence, but the steps for other apps are similar
Hi,
this won't work, as Atlassian strongly recommends to NOT RUN MORE THAN ONE PRODUCT on a single server. What you can do is having a single HTTP-Server (Apache, IIS,..) running on port 80 facing the customers/users (Frontend-Server) and serving the applications (Confluence, Jira, Bitbucket) (Backend-Server) via e.g. AJP on port 8090. I've no experience with IIS as HTTP-server and can only point our that Apache 2.4 is running without flaws using this configuration. Try running the Atlassian products on virtual servers on your Windows server. Depending on the user size each product would need about 4-6GB RAM initially...
You can try, but I STRONGLY do not recommend this, running the single products on different ports (8009, 8010, 8011) and configure the HTTP-Server to listen to the different ports, but I'm pretty sure you will run into trouble having more than a single JVM running on a single server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.