Difference between revisions of "Web-server-stack"
Threesixes (talk | contribs) (fix initial commit blunders) |
Threesixes (talk | contribs) m (add section about ssl wild card url considerations, bumped email to pre install so ssl certs and verification can be mailed to the server in question.) |
||
| Line 1: | Line 1: | ||
== Pre-install considerations == | |||
Ssl wild card certificates can use the same certificate to cover several subdomain names. As in https://wiki.funtoo.org https://www.funtoo.org https://forums.funtoo.org can all use the same certificate. https://funtoo.org would not be covered under the wildcard, so [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) suggests using http://domain.tld as a http navigation splash page directory. All that is required to setup a ca signed ssl certificate is an email on the server. Click [https://www.startssl.com here] for a free ssl ca cert. Some web applications have http hard coded into the css style sheets urls instead of using relative urls, so they need to be changed to https or relative if you lose your styles. | |||
=== Email Servers === | |||
*[[Package:Ssmtp|Ssmtp]] | |||
*[[Package:Postfix|Postfix]] | |||
*[[Package:Exim|Exim]] | |||
*[[Package:Sendmail|Sendmail]] | |||
== Webserver == | |||
Web servers come in several varieties. The most common stack is known as LAMP which stands for linux apache mysql php. [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) suggests setting up the web server stack by selecting the database first, then scripting language second, and web server 3rd. | Web servers come in several varieties. The most common stack is known as LAMP which stands for linux apache mysql php. [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) suggests setting up the web server stack by selecting the database first, then scripting language second, and web server 3rd. | ||
=== Databases === | === Databases === | ||
*[[Package:MySQL|MySQL]] | *[[Package:MySQL|MySQL]] | ||
| Line 20: | Line 30: | ||
== Post install == | == Post install == | ||
There are several considerations to take into account with a web server install, such as setting up an email server, setting up a firewall, firewalling web applications, and dynamically firewalling attackers. | There are several considerations to take into account with a web server install, such as setting up an email server, setting up a firewall, firewalling web applications, and dynamically firewalling attackers. | ||
=== Firewalls === | === Firewalls === | ||
Revision as of 09:29, September 2, 2014
Pre-install considerations
Ssl wild card certificates can use the same certificate to cover several subdomain names. As in https://wiki.funtoo.org https://www.funtoo.org https://forums.funtoo.org can all use the same certificate. https://funtoo.org would not be covered under the wildcard, so Threesixes (talk) suggests using http://domain.tld as a http navigation splash page directory. All that is required to setup a ca signed ssl certificate is an email on the server. Click here for a free ssl ca cert. Some web applications have http hard coded into the css style sheets urls instead of using relative urls, so they need to be changed to https or relative if you lose your styles.
Email Servers
Webserver
Web servers come in several varieties. The most common stack is known as LAMP which stands for linux apache mysql php. Threesixes (talk) suggests setting up the web server stack by selecting the database first, then scripting language second, and web server 3rd.
Databases
Languages
Web Servers
Post install
There are several considerations to take into account with a web server install, such as setting up an email server, setting up a firewall, firewalling web applications, and dynamically firewalling attackers.