Feeds, issues, packages and code source about emulation and pograming, of VENENUX proyects, Debian related distros and massenkoh!

Why SourceForge instead GitHub?

|

Why SourceForge instead of GitHub?

The answer is actually quite simple, the only reason, GitHub doesn't offer a place to upload packages (just a master package) and then provide statistics on those files. SourceForge does provide that feature and even breaks it down on a daily, weekly, monthly, annually, and all time statistics. Of course, too complex, heavy and get many workload on client side on browsers, but provide it and with a lot of space!!!.

Why GitHub instead SourceForge?

A poor but easy reson, guindoser like of course: easy to use and lightweith interface, not much usefully but great for little projects.

Conclusion?

For mayor projects that need heavywheith features with stitcs and great control: SF, 
For little and short time things, Github for novices.

debian jessie

|
Debian jessie are now stable an i now back to squeeze, with etch, lenny are now freeze for me, so then, working now in finish sysvinit/hal era of linux and started the new systemd/udev era
Ian was gone! and new stuffs comes to Debian, many caused breaks, like the rumors of fork of it! Ian Murdok the father of Debian project always thing about proyections but today that its a M$ like enterprice!

STARTING A NEW ERA: THE CHANGES AND WHEEZE

With this release, hal and sysvinit has end, the "hard-forced" systemd from win-hat guys are a fact and udev/upower/udisk are the new devices managers.

The wheeze release was only a "transitional release" like sarge does and lenny/etch does!

The UEFI support was added but not as totally free software. UEFI uses a firmware check so has a closed object check at boot. The boot areenabled in 32 and 64 bits archs.

Multiarch is a radical rethinking of the filesystem hierarchy with respect to library and header paths, to make programs and libraries of different hardware architectures easily installable in parallel on the very same system. So with this i386 and x64 can be both packages instalable in same machine. Of couse be prepared to a lot of space consume, its like have a duplication of.

Media installers reduced: yes now all come to the net, only a set of 4 DVD's or 12 CD's are made, the rest of sofware are in the repositories.

Mate, cinnamon are new desktop, in the old-school fashion scene, and now backport are in main as normal repository!

CONCLUSION: THE WINDO-LIKE STUPID ERA BEGIN!

Personally now the linux scenary are like the M$ does, a windo-like systems with huge of complex requeriments and user-oriented stupid things. Minimun requeriments are raised now from 200MHz with 128Ram for a GTK/qt desktop to a minimun of 1GHz with 1GB Ram for decent web browsing!

U are forced to use those if comes for frowsing and use recent hardware and recent stuff need this recent release of jessie! There's no way, other than VenenuX 0.X series or the recent Debian/VenenuX releases.

Web Server Choice and Comparison Tables

|

Web Server Choice and comparision tables


  1. Apache: heavyweight
  2. Nignx vs Lighttpd
  3. Hiawatha the most secure
  4. Comparision table/Tabla comparativas
  5. Conclusion
.
Sources: http://vegnuli.needthis.net/Web_Server__Choice


A server choice comparision u must read, venenux only comes with update packages of lightttpd and hiawatha, due no-one of two offers all the necesary.


Una comparacion de escogencia en servidor web que debe leer, venenux solo empaqueta lighttpd y hiawatha, ya que ninguno de lso dos ofrece todo lo necesario.


APACHE: Heavyweith/Peso Pesado


Apache is at the core of the L.A.M.P. technology stack upon which a lot of server architecture is based: Linux, Apache, MySQL, PHP; so many use L.A.M.P. as a foundation. Among them are CMSs as Drupal or WordPress; and Apache modules enable you to easily incorporate additional functionalities. For windozers or novice developers.


In general, neither Apache nor IIS are lightweight or fast. If you want the maximum number of Web pages, static or dynamic, served in the fastest possible time with the minimum of resources, you need to look beyond the big two.


For starters, Apache doesn’t scale well, additional requests spawns new threads (i.e., processes); more connections, more processes are spawned, and your Web server can become memory starved.


Apache es el nucleo de L.A.M.P. conjunto de tecnología sobre la que se basa una gran cantidad de arquitectura de servidor: Linux, Apache, MySQL, PHP, por lo que muchos utilizan L.A.M.P como una fundacion. Entre ellos estan los CMS como Drupal o WordPress, y modulos Apache le permiten fácilmente incorporar funcionalidades adicionales. Para el windosero en fin.

En general, ni Apache ni IIS son ligeros o rapidos. Si desea que el numero maximo de paginas Web, estatica o dinamica, que se sirve en el menor tiempo posible con el mínimo de recursos, es necesario mirar mas alla de los dos grandes.

Para empezar, Apache no escala bien, las solicitudes adicionales desova nuevos hilos (es decir, procesos); mas conexiones, mas procesos se generan y el servidor Web puede convertirse en un comedor de memoria.


NIGNX vs LIGHTTPD: eficientes


Nginx is an Web server that includes an Reverse Proxy, an Internet Message Access Protocol (IMAP) and Post Office Protocol (POP) server. The single most important reason why companies use Nginx is that its asynchronous architecture gives it a small memory footprint and low resource consumption. Nginx is asynchronous event-based, so it doesn't spawn new processes or threads for each Web page request: even as the load increases, memory use remains predictable; so can take a lot of beating from users highly efficiently.


Nginx es un servidor web que incluye un Proxy Inverso, un protocolo de acceso a mensajes de Internet (IMAP) y Post Office Protocol servidor (POP). La razón mas importante por la cual las empresas utilizan Nginx es que su arquitectura asincrona le da una pequeña huella de memoria y un bajo consumo de recursos. Nginx es Basado-En-Eventos asi­ncrono, por lo que no desova nuevos procesos o hilos para cada solicitud de página Web: aun cuando la carga aumenta, el uso de memoria sigue siendo predecible, de modo que puede tomar un montón de golpes de usuarios altamente eficiente.


Lighttpd, pronounced "lightly" powers such sites as some Google services (speciallyYouTube) and Wikipedia. That's taking many about. Focused on keep alive the contract between server and client one stabliced. Uses an event-driven architecture optimized for a large number of parallel connections (keep-alive) which is important for high performance Ajax applications. The good choose for Web sites that use the Ajax Web application design model and Web 2.0 apps (such Wordpress, Joomla) with high demand of request for dinamic contents that becomes static one generated. Its high dificulty for configuring if u dont know what u doin.


Lighttpd, que se pronuncia "laighti" sirve a todo google (especialmente YouTube) y Wikipedia. Eso dice mucho de el. Centrado en mantener vivo el contrato entre el servidor y el cliente; utiliza una arquitectura Orientada-A-Eventos optimizado para un gran numero de conexiones en paralelo (keep-alive) que es importante para las aplicaciones Ajax de alto rendimiento. Indicado para los sitios Web que utilizan el Ajax modelo de diseño de aplicaciones Web y/o aplicaciones Web 2.0 (como Wordpress,Joomla) con alta demanda de solicitud de contenidos dinamicos que se convierte en una estatica una vez generados. Es dificil de configurar si no se sabe lo que se hace.


HIAWATHA: Segurity and performance/Seguridad y rendimiento


The real concern is running a secure Web site: so the Hiawatha Web server. Comes along with own balanced fast-cgi engine for php server, build in reverse proxy and cached keep-alive conectios, prepared for the secure Banshee PHP Web site framework, and a Hiawatha Monitor with build in web request firewall. Most security: where HTTPS used, rather than use the sometimes broken OpenSSL for Secure Socket Layer (SSL) connections, Hiawatha uses the historically high secure PolarSSL.


This ist a paranoid web server with all need features.


La verdadera preocupación es colocar un sitio Web seguro: lo que el servidor Web Hiawatha. Viene incluido con manejador especial balanceado de cgi de php, proxy inverso y conecciones de mantener activa la memoria caché; esta diseñado preparado para la infraestructura de sitio Web seguro Banshee PHP, y un monitor de Hiawatha con estructura en solicitud Web firewall. Mas seguridad: donde HTTPS utiliza, en lugar de utilizar el OpenSSL siempre fallando para Secure Socket Layer (SSL), Hiawatha utiliza la historicamente ultra segura PolarSSL.


Esto es un servidor web ultra seguro con todo lo necesario.


Table comparision of features of popular web servers


Tabla comparativa de caracteristicas de web server populares

.


Server


Developed


License


Apache HTTP Server


Apache Software Foundation


Apache


Cherokee HTTP Server


Álvaro López Ortega


GPL


Hiawatha HTTP Server


Hugo Leisink


GPLv2


Yaws


Claes Wikström


GPL


lighttpd


Jan Kneschke


BSD variant


Nginx


NGINX, Inc.


BSD variant


Features/Caracteristicas



link to wikipedia


Basic authentication

Digest authentication

SSL/TLS https

Virtual hosting

CGI

FCGI

SCGI

WSCGI

SSI

ISAPI

Userland kernelspace

Admin console

IPv6

Apache HTTP Server


Yes


Yes


Yes


Yes


Yes


Yes


Yes


Yes[b]


Yes


Yes[d]


user


Yes[e]


Yes


Caudium


Yes


Yes


Yes


Yes


Yes


Yes


Unknown


No


Yes


Unknown


user


Yes


Yes[i]


Cherokee HTTP Server


Yes


Yes


Yes


Yes


Yes


Yes


Yes


Yes


Yes


No


user


Yes


Yes[1]


Hiawatha HTTP Server


Yes


Yes


Yes


Yes


Yes


Yes


No


No


Yes


No


user


Yes


Yes


lighttpd


Yes


Yes


Yes


Yes


Yes


Yes


Yes


No


Yes


No


user


No


Yes


NaviServer


Yes


No


Yes


Yes


Yes


No


Unknown


No


No


Unknown


user


Yes


Unknown


nginx


Yes


Yes


Yes


Yes


No


Yes


Yes


Yes


Yes


No


user


Yes[5]


Yes[6]


thttpd


Yes


Unknown


No


Yes


Yes


No


Unknown


No


No


No


user


No


Yes


TUX web server


No


No


No


Yes


Yes


No


Unknown


No


No


No


kernel


Unknown


Unknown


Yaws


Yes


Unknown


Yes


Yes


Yes


Yes


Unknown


No


Yes


No


user


Unknown


Yes

.


Conclusiones


Small businesses: the obvious choice is not to waste time on maintenance and safety , sleeping so calm and concentrate on other things and not on the website, so hiawatha is recommended. If the company level, or nonpersonal services offers dynamic content with high scalability is recommended lighttpd.

Corporations : a single web server software is not recommended when you have multiple services, best is delegated all services by finnality. Lower demand services but sensitive information: hiawatha is the choice. And for high demand services but trivial information: lighttpd is the choice. Combining the two in each section which is better, the corporate intranet is served efficiently.

Developer : due the issue here is to finish the order, and like most frameworks are for apache and nignx, would be recommended; but when deploying to production is another matter, so lighttpd is something to consider if the result relies on scalability respect performance and compatibility.

General use: The obvious choice is given lighttpd is more compatible with most frameworks , and offers most of the features that are already in nignx apache. Besides having a humble consumer .

Newbie: nignx or apache due will not have the capacity or habilities like the champions does for use lighttpd or hiawatha .


In order of suggestions taken in consideration all features and performance, event the security:


  1. lighttpd: high scalability and performance, dificil de configurar.
  2. hiawatha: paranoid security and internal networks, most secure.
  3. nignx: compatibility and faster deployment
  4. apache: for windozers and novices

Pequeñas empresas: la opcion obvia es no desperdiciar tiempo en mantenimiento y seguridad, asi que para dormir tranquilo y concentrarse en otras cosas y no en el sitio web, hiawatha es lo recomendado. Si la empresa escala, o ofrece servicios de contenido dinamico no personales, recomendable es alta escalabilidad con lighttpd.


Grandes empresas: un unico software servidor web no es recomendable, cuando se tiene multiples servicios mejor es delegar. Para servicios de baja demanda pero de delicada informacion: hiawatha es la eleccion. Para los servicios de alta demanda pero informacion trivial, lighttpd es la eleccion. Combinando los dos en cada apartado donde es mejor, se sirve la intranet empresarial eficientemente.


Desarrolladores: debido el tema es terminar lo pedido, y como la mayoría de los frameworks son para apache y nignx, seria lo recomendado; pero al implementar a producción la cosa cambia, asi que lighttpd es algo de tomar en cuenta, si el resultado tiende a la escalabilidad y compatibilidad.


Uso general: la eleccion obvia es lighttpd dado es el mas compatible, con la mayoria de los frameworks, y ofrece la mayoria de las caracteristicas de nignx que ya estan en apache. Ademas de tener un consumo humilde.


Novatos: apache o nignx, ya que no tendran la destreza para usar software para campeones como lighttpd o hiawatha.


En orden de sugerencia, tomando en consideracion las caracteristicas y rendimiento, aun asi la seguridad:


  1. lighttpd: alta escalabilidad y rendimiento, altamente eficiente y dificil.
  2. hiawatha: para contenido sensible y redes internas, el mas seguro.
  3. nignx: para rapida implementacion
  4. apache:  para windoseros o novatos