Skip to content

Conversation

@kulga
Copy link
Contributor

@kulga kulga commented May 25, 2016

Resolves flarum/framework#955
#955


### Nginx

Add the following lines to your server's configuration block:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line would be changed...

@franzliedke
Copy link
Contributor

I'm not 100% sure about this.

We would probably need some more explanation / details about which parts are needed when, and what they mean.

@tobyzerner
Copy link
Contributor

Yep, we were discussing this in the meeting. I think the conclusion we came to was that we should add some comments next to the placeholder lines that need to be changed.

And should we change the intro line to something like "Your nginx server configuration should look something like this:" ?

@kulga
Copy link
Contributor Author

kulga commented May 25, 2016

I was thinking a few ways to do this

  • inline
  • a more elaborate multi-line explanation
  • examples and explanation
  • examples and referential links

Eg

    listen 80; # HTTP, use 443 ssl for HTTPS. Can also be 1.2.3.4:80
# listen defines the port used. 80 is used for http
# 443 and ssl are used for listening to https connections
# and require certificate configuration to work properly
listen 80;
# listen defines the port used. 80 is used for http
# 443 and ssl are used for listening to https connections
# and require certificate configuration to work properly
# If using ssl uncomment the following line

# listen 443 ssl;
listen 80;
# listen defines the port used. 80 is used for http
# See this link for more details
# http://nginx.org/en/docs/http/ngx_http_core_module.html#listen

listen 80;
# listen 443 ssl;

@franzliedke
Copy link
Contributor

I vote inline.

IMO, a big problem with Nginx configs in the internet are mostly trying to copy some stuff together until it works, without knowing why or how to do it better. (Note, I don't exclude myself from that.) That probably also says about the power / usability of these configs...

@luceos
Copy link
Member

luceos commented Sep 22, 2016

I think inline will not give us the opportunity to explain what it does sufficiently. I like the multi line solution better..

@franzliedke
Copy link
Contributor

@kulga Can you adapt this accordingly?

@tobyzerner
Copy link
Contributor

@kulga bump :) are you able to do this still?

@franzliedke
Copy link
Contributor

@kulga May I nudge you again? Otherwise, anybody else interested in taking this over?

More commentary
@kulga
Copy link
Contributor Author

kulga commented Feb 3, 2017

I put some commentary in.
I also included a part for HTTPS encryption.

Unfortunately, I'm shorter on time now. It may well be better to have someone that can dedicate more time to this complete this :)

@tobyzerner
Copy link
Contributor

tobyzerner commented Dec 22, 2017

I don't know if we should have config for SSL in here. I feel like it's outside the scope of what we need to provide. Perhaps a link to a good page/guide would suffice.

@franzliedke
Copy link
Contributor

@tobscure Agreed. The more we provide, the more we need to keep up-to-date / in sync for the different server platforms.

@tobyzerner
Copy link
Contributor

@franzliedke I think this can be closed actually. We've removed non-Flarum-specific config from the nginx.conf we distribute in flarum/flarum. It's the user's responsibility to do the rest of their config, we don't need to document it.

@tobyzerner tobyzerner closed this Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants