Differences between revisions 43 and 46 (spanning 3 versions)
Revision 43 as of 2009-11-16 23:37:50
Size: 1030
Editor: fruity
Revision 46 as of 2009-12-03 00:39:31
Size: 863
Editor: fruity
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
== My pages: == == My pages /|\ Le mie pagine ==
Line 9: Line 9:

=== Multimedia ===
Line 13: Line 15:
=== Admin notes ===
Line 16: Line 20:
=== Programming notes ===
Line 18: Line 24:

=== Web notes ===
Line 27: Line 35:
== Messed up pages /|\ Pagine incasinate ==

[[icecast-2.3.2-kh8|Icecast2-kh]] <!> to be removed/renamed soon <!>

[[fruity/FruityHomeCluster|Notes on my home cluster setup]]

[[MoinMoinFarmingApache2WSGI|How to set up MoinMoin 1.8.5 in farm mode on apache2 with wsgi]]

\o) [[ fruity ]] (o/

Email: fruity@freaknet.org q[9c9]p

My pages /|\ Le mie pagine

  • This is a bunch of notes, personal howtos and ideas.


Admin notes

Programming notes

Web notes

  • Web notes:

    • 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.

          Yet Another Web Server(in erlang)

      • 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.


      MoinMoin farm


      Django notes

Contributed pages /|\ Pagine contribuite


fruity (last edited 2010-12-01 13:21:14 by anonymous)