Differences between revisions 31 and 35 (spanning 4 versions)
Revision 31 as of 2009-11-04 20:45:17
Size: 863
Editor: fruity
Comment:
Revision 35 as of 2009-11-04 20:53:02
Size: 868
Editor: fruity
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
This is a bunch of notes, personal howtos and ideas.  This is a bunch of notes, personal howtos and ideas.
Line 9: Line 9:
[[fruity/Multimedia|Multimedia:]]
<<Include(fruity/Multimedia)>>
 * [[/Multimedia|Multimedia:]]
   <<Include(fruity/Multimedia)>>
Line 12: Line 12:
[[fruity/AdminAndConfs|Admin notes:]]
<<Include(fruity/AdminAndConfs)>>
 * [[/AdminAndConfs|Admin notes:]]
   <<Include(fruity/AdminAndConfs)>>
Line 15: Line 15:
[[fruity/Web|Web notes:]]
<<Include(fruity/Web)>>
 * [[/Web|Web notes:]]
   <<Include(fruity/Web)>>
Line 18: Line 18:
[[fruity/django|Django notes]]
<<Include(fruity/django)>>
 * [[/django|Django notes]]
   <<Include(fruity/django)>>
Line 24: Line 23:
[[fruity/Contrib|Contribuited pages]]
<<Include(fruity/Contrib)>>
 * [[fruity/Contrib|Contribuited pages]]
   <<Include(fruity/Contrib)>>

== \o) fruity (o/ == Email: fruity@freaknet.org q[9c9]p

My pages:

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

  • Admin 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:

          Pound

          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.

      Wikis

      MoinMoin farm

      FrameWorks

      Django notes

  • Django notes

    • Describe fruity/django here.

Contributed pages /|\ Pagine contribuite

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


CategoryHomepage

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