Apache2 Gets Installed Regardless
rimckenn opened this issue · 6 comments
From the docs, the default stash recipe should configure Stash under Tomcat only, but the recipe includes the apache2 recipe so apache2 always ends up being installed.
I think the default recipe does the right thing in spirit by configuring a front end with port 80 and 443 for ease of Stash UI use, but the documentation should probably mention the Apache httpd setup. Custom setups can choose the exact recipes they need if the default doesn't suit them.
Is this what you would have expected? I'll get that documentation fixed up if that's the case.
Out of curiosity, how are you looking to setup your environment beyond just Stash running on Tomcat if you didn't want httpd? Nginx in front on the node? Load balancer directly to Tomcat? Having users connect directly to Tomcat port?
Hi Brian, cheers for getting back to us so quickly.
If that is the intention, then updating the documentation sounds like the right thing to do.
There are just a few of using Stash here so the plan is to just connect to the Tomcat port directly (do you think that will cause problems?) - we don't need SSL either as it is all over VPN and not publicly available. The problem is that we are running it on a server that is already using the SSL port so the apache recipe always fails. I like to use the recipe because it configures the db, user and sets it up as a service which is very nice!
I did try running it without the apache recipe, but then because it had run once before, I had an apache node created on the host so all the subsequent runs try to configure it for apache anyway. I deleted the apache attributes from the node and reran it, but it still didn't work as the tomcat ssl didn't seem to work. Not sure if that was to do with the SSL key being created in a path that didn't exist.
I'm just getting started with Stash so in the end I just installed it manually, but would hope to try your recipes when I get some more time in the future.
Many thanks,
Richard
I've updated the README documentation to mention the Apache httpd installation for the default recipe and removed some of the old information. If I have time, I'll add another section on running on straight Tomcat without httpd. Thanks for the details!
Cheers Brian!
On 4 Nov 2013, at 05:11, Brian Flad notifications@github.com wrote:
I've updated the README documentation to mention the Apache httpd installation for the default recipe and removed some of the old information. If I have time, I'll add another section on running on straight Tomcat without httpd. Thanks for the details!
—
Reply to this email directly or view it on GitHub.
I could not figure out how to disable apache install.
Something is extremely fishy with this cookbook, specifically when using self-signed certificates and deploying one to apache and same via keystore to tomcat... while stash seems functional, linking stash to other Atlassian applications does not seem to work. My gut feeling was to disable apache and try to work these problems using tomcat+ssl alone. So far, I didn't get too far - probably because I'm using a wrapper around stash cookbook and did not yet have the courage to gut stash cookbook itself.
Any pointers? Documentation updates?
We are also using Stash without any HTTPD in front as Stash is behind a load balancer which does SSL offloading as well. Is there a possibility to use the cookbook without Apache...?