Differences between revisions 35 and 38 (spanning 3 versions)
Revision 35 as of 2009-11-04 20:53:02
Size: 868
Editor: fruity
Comment:
Revision 38 as of 2009-11-16 23:31:20
Size: 956
Editor: fruity
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 5:
=== My pages: === == My pages: ==
Line 18: Line 18:
 * [[/django|Django notes]]
   <<Include(fruity/django)>>

=
== Contributed pages /|\ Pagine contribuite ===
== Contributed pages /|\ Pagine contribuite ==
Line 26: Line 23:
=== Messed up pages /|\ Pagine incasinate === == Messed up pages /|\ Pagine incasinate ==
Line 34: Line 31:
{{{#!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

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

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)