Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide Documentation/Guidance on Deploying Boot Applications to Production #2385

Closed
rwinch opened this issue Jan 20, 2015 · 3 comments
Closed
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: documentation A documentation update

Comments

@rwinch
Copy link
Member

rwinch commented Jan 20, 2015

The current Spring Boot documentation does provide documentation on using Spring Boot behind a proxy and how to enable SSL. However, it could be improved to include:

  • How to setup load balancing. Some documentation and a config example on how to use nginx might be useful for this.
  • How to support clustered environments (i.e. Sessions)

Related #1117 #2071

@philwebb philwebb added the type: documentation A documentation update label Jan 29, 2015
@philwebb philwebb added this to the 1.3.0 milestone Jan 29, 2015
@philwebb philwebb modified the milestones: 1.3.0.RC2, 1.3.0.RC1 Jul 10, 2015
@snicoll snicoll modified the milestones: 1.3.0, 1.3.0.M5 Aug 26, 2015
@sloppycoder
Copy link

I'm working on these 2 topics. so far I have got clustering to work with spring-session with last code on master, but still having trouble with nginix SSL proxy setup.

Please provide some guideline and I'd like to contribute.

@philwebb philwebb modified the milestones: 1.3.1, 1.3.0 Nov 13, 2015
@philwebb
Copy link
Member

The session information would be useful but I don't think we should include nginx details in the core reference guide. A stand-alone guide on spring.io would be very welcome though.

@philwebb philwebb modified the milestones: 1.3.2, 1.3.1 Dec 17, 2015
@philwebb philwebb modified the milestones: 1.4.0.RC1, 1.3.2, 1.4.0 Jan 21, 2016
@philwebb philwebb removed this from the 1.4.0 milestone Jul 27, 2016
@philwebb
Copy link
Member

We're cleaning out the issue tracker and closing issues that we've not seen much demand to fix. Feel free to comment with additional justifications if you feel that this one should not have been closed.

@philwebb philwebb added the status: declined A suggestion or change that we don't feel we should currently apply label Mar 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: documentation A documentation update
Projects
None yet
Development

No branches or pull requests

4 participants