|
Size: 868
Comment:
|
Size: 959
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == \o) [[fruity]] (o/ == Email: fruity@freaknet.org '''q[9c9]p''' | = \o) [[ fruity ]] (o/ = Email: fruity@freaknet.org '''q[9c9]p''' |
| Line 5: | Line 6: |
| === My pages: === | == My pages: == |
| Line 18: | Line 19: |
| * [[/django|Django notes]] <<Include(fruity/django)>> === Contributed pages /|\ Pagine contribuite === |
== Contributed pages /|\ Pagine contribuite == |
| Line 26: | Line 24: |
| === Messed up pages /|\ Pagine incasinate === | == Messed up pages /|\ Pagine incasinate == |
| Line 34: | Line 32: |
| {{{#!wiki comment/dotted This is a wiki parser section with class "comment dotted" (see HelpOnParsers). Its visibility gets toggled the same way. }}} |
\o) [[ fruity ]] (o/
Email: fruity@freaknet.org q[9c9]p
Contents
My pages:
- This is a bunch of notes, personal howtos and ideas.
This are my notes on multimedia stuff:
Notes on my home computer cluster made of piles of ol'cheap hardware. The idea is to give a use to all old hardisks and platforms for having a reliable network storage / fileserver
Notes on setting multiple moinmoin wiki.
Notes on the pratice of virtualizing computers
Create and maintain a Debian repository
My notes and points of view on security.
Breaking the LAMP loop, alternative web serving methods
Lately I decided to look elsewhere than the usual "linux apache mysql php". Reading on docs makes me draw something like apache or ngingx as a load balancer front-end, the same as the backend adding lighttpd for fast streaming ofdata. This leave me more confused than before:
- apache or ngingx? old but solid or new with an ongoing development? wich for load and wich for serving?
- My head started to wirl and I thought myself using a beast like apache to do load balancing was a bit like killing a fly with a nuke, so for I looked elsewhere for a solution and apt-cache search came to the rescue:
The config file is one placed in /etc/pound/pound.conf, is very simple and straight forward.
Pound Reverse proxy, load balancer and HTTPS front-end for Web servers
For the serving of static/dynamic content I decided that also for serving apache wasn't good enough, I looked over webrick and was not stable enough, I looked over python-wisted and it wasn't fast enough and so I found YAWS (Yet Another Web Server) written in erlang designed for performance and scalability over multiple servers.
- My head started to wirl and I thought myself using a beast like apache to do load balancing was a bit like killing a fly with a nuke, so for I looked elsewhere for a solution and apt-cache search came to the rescue:
- database: mysql?postgres?sqlite?ORACLE!??
- I need to have the vastest gamma of databases, I want to be able to store certain data to certain databases and I want to be able to do certain query over different databases.
For this to work there is a huge amount of changes to be done in software but yet so far there is SQLAlchemy and DBSlayer. I will investigate databases soon enough.
- I need to have the vastest gamma of databases, I want to be able to store certain data to certain databases and I want to be able to do certain query over different databases.
Wikis
FrameWorks
- apache or ngingx? old but solid or new with an ongoing development? wich for load and wich for serving?
Contributed pages /|\ Pagine contribuite
This are the pages I('ve) contribute(d):
Messed up pages /|\ Pagine incasinate
Icecast2-kh 
to be removed/renamed soon
Notes on my home cluster setup
How to set up MoinMoin 1.8.5 in farm mode on apache2 with wsgi