Difference between pages "Merge Funtoo 1.0 profile support into gentoo" and "Web-server-stack"

(Difference between pages)
(Created page with "Steps to merge funtoo 1.0 style profile support into gentoo: 1.) eselect-profile support We want eselect-profile to support both the funtoo style profiles and the gentoo...")
 
m (Benchmarking: MOAR)
 
Line 1: Line 1:
Steps to merge funtoo 1.0 style profile support into gentoo:
 
  
1.) eselect-profile support
+
== Pre-install considerations ==
    We want eselect-profile to support both the funtoo style profiles and the gentoo style profiles at the same time
+
=== ssl ===
    First thought, says if /etc/{,portage}/make.profile is a symlink, only show gentoo style profiles; this will hide the changes from unsuspecting users so they don't   
+
Ssl [http://en.wikipedia.org/wiki/Wildcard_certificate 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.  https://www.startssl.com offers free ssl ca certificates, though there are several other certificate [http://en.wikipedia.org/wiki/Certificate_authority#Providers providers].  Many web apps require you set your URL & will have problems if your URL is set to http://, rather than https://
        accidently set an experimental profile as gentoo tries to catch up.
+
 
    If /etc/{,portage}/make.profile is not a symlink, then show a list of old style profiles and new style profiles.
+
=== sockets vs tcp stack ===
        This may require funtoo to remove profiles.desc and profiles.eselect.desc from gentoo before replicating.
+
Sockets have less overhead but can not be shared across jails, or to other machines.  Tcp stack has more overhead but is far more flexible.
2.) catalyst support
+
 
    seems trivial, support catalyst setting new style profiles.
+
=== Email Servers ===
    input requested from funtoo team on suggested syntax
+
* {{Package|mail-mta/postfix}}  <-- suggested
3.) build prototype profiles in gentoo for all possible x86/amd64 varients.
+
* {{Package|mail-mta/ssmtp}}
    mgorny has some good ideas here for multilib stuff
+
* {{Package|mail-mta/exim}}
    blueness has some good ideas for hardened and alternative libc implementations
+
* {{Package|mail-mta/sendmail}}
 +
* {{Package|mail-mta/nullmailer}}
 +
 
 +
=== FTP Servers ===
 +
It is common practice to use FTP servers to host files for downloading.
 +
 
 +
* {{Package|net-ftp/vsftpd}} <-- suggested
 +
* {{Package|net-ftp/proftpd}}
 +
* {{Package|net-ftp/pure-ftpd}}
 +
* {{Package|net-ftp/qshare}}
 +
 
 +
== 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.
 +
 
 +
=== Databases ===
 +
* {{Package|dev-db/mysql}}
 +
 
 +
mariadb is a drop in replacement for mysql
 +
* {{Package|dev-db/mariadb}} <-- suggested
 +
 
 +
percona is a drop in replacement for mysql
 +
* {{Package|dev-db/percona-server}}
 +
 
 +
* {{Package|dev-db/postgresql-server}}
 +
* {{Package|dev-db/sqlite}}
 +
 
 +
=== Languages ===
 +
* {{Package|dev-lang/php}} <-- suggested
 +
* {{Package|dev-lang/perl}}
 +
* {{Package|dev-lang/python}}
 +
 
 +
=== Web Servers ===
 +
* {{Package|www-servers/apache}}
 +
* {{Package|www-servers/cherokee}}
 +
* {{Package|www-servers/nginx}} <-- suggested
 +
* {{Package|www-servers/tengine}}
 +
* {{Package|www-servers/lighttpd}}
 +
 
 +
 
 +
=== SSL Termination, Reverse Proxies, & load balancing ===
 +
Reverse proxies are useful, some cache static data, and shuck out cached pages rather than hitting the web server. Some pass requests to backend nodes high availability clustering your website, some web servers have this functionality built in.
 +
 
 +
* {{Package|www-servers/nginx}}
 +
* {{package|net-misc/stunnel}}
 +
* {{package|www-servers/pound}} <-- suggested for ssl termination & load balancing
 +
* {{Package|www-servers/varnish}} <-- suggested for caching to reduce power consumption & reduce the need of constantly rebuilding pages
 +
* {{Package|net-proxy/squid}}
 +
 
 +
== 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.
 +
 
 +
=== Firewalls ===
 +
* {{Package|net-firewall/nftables}}
 +
* {{Package|net-firewall/iptables}} <-- suggested
 +
* {{Package|net-firewall/firewalld}}
 +
* {{Package|net-firewall/ufw}}
 +
 
 +
=== Dynamic Firewalling ===
 +
* {{Package|app-admin/sshguard}} <-- suggested
 +
* {{Package|net-analyzer/fail2ban}}
 +
 
 +
=== Webapp Firewalls ===
 +
 
 +
Apache has an option for webapplication firewalling. as far as [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) can tell this passes login errors & excessive site fuzzing to logs for fail2ban/sshguard to deal with.
 +
https://github.com/nbs-system/naxsi is a web app firewall for nginx.
 +
 
 +
=== Benchmarking ===
 +
It's a good idea to benchmark your system, server, & websites.  There are several tools to assist you in doing this.
 +
 
 +
* http://toolbar.netcraft.com/site_report?url=undefined#last_reboot
 +
* http://gtmetrix.com/
 +
* http://www.showslow.com/
 +
* http://yslow.org/
 +
* http://getfirebug.com/
 +
* {{Package|app-admin/apache-tools}}
 +
* {{Package|app-benchmarks/sysbench}}
 +
* {{Package|app-benchmarks/phoronix-test-suite}}
 +
* {{Package|app-benchmarks/iozone}}
 +
* {{Package|app-benchmarks/piozone}}
 +
* {{Package|app-benchmarks/siege}}
 +
* {{Package|app-benchmarks/ramspeed}}
 +
* {{Package|app-benchmarks/jmeter}}

Latest revision as of 13:55, January 18, 2015

Pre-install considerations

ssl

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. https://www.startssl.com offers free ssl ca certificates, though there are several other certificate providers. Many web apps require you set your URL & will have problems if your URL is set to http://, rather than https://

sockets vs tcp stack

Sockets have less overhead but can not be shared across jails, or to other machines. Tcp stack has more overhead but is far more flexible.

Email Servers

FTP Servers

It is common practice to use FTP servers to host files for downloading.

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

mariadb is a drop in replacement for mysql

percona is a drop in replacement for mysql

  • dev-db/percona-server (package not on wiki - please add)
  • dev-db/postgresql-server (package not on wiki - please add)
  • dev-db/sqlite (package not on wiki - please add)

Languages

Web Servers


SSL Termination, Reverse Proxies, & load balancing

Reverse proxies are useful, some cache static data, and shuck out cached pages rather than hitting the web server. Some pass requests to backend nodes high availability clustering your website, some web servers have this functionality built in.

  • Nginx
  • net-misc/stunnel (package not on wiki - please add)
  • www-servers/pound (package not on wiki - please add) <-- suggested for ssl termination & load balancing
  • Varnish <-- suggested for caching to reduce power consumption & reduce the need of constantly rebuilding pages
  • Squid

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.

Firewalls

Dynamic Firewalling

Webapp Firewalls

Apache has an option for webapplication firewalling. as far as Threesixes (talk) can tell this passes login errors & excessive site fuzzing to logs for fail2ban/sshguard to deal with. https://github.com/nbs-system/naxsi is a web app firewall for nginx.

Benchmarking

It's a good idea to benchmark your system, server, & websites. There are several tools to assist you in doing this.