PUBLIC MARKS from camel with tag tutorial

Cet article est une traduction de CSS 2.1 selectors, Part 1, écrit par Roger Johansson pour son blog 456 Berea Street. Une des premières choses à comprendre lorsque l'on commence à étudier les CSS sont les sélecteurs. Il s'agit évidemment d'une partie fondamentale des CSS, mais peu de développeurs les utilisent à leur plein potentiel. Même si beaucoup peut être fait avec les seuls sélecteurs de type, d'ID et de classes, il en existe bien d'autres.

This tutorial shows how to install and configure the Zenoss network monitoring tool on a Ubuntu 6.06 system. Zenoss is a free open-source tool that allows you to monitor servers, applications, networks, power, etc. regarding their configuration, availability, performance, and so on. It can also alert you by email if it finds inappropriate actions.

Ces différents exemples ont été initialement conçues pour illuster une conférence CSS donnée en mai 2006.

TUTMARKS est un site web collaboratif spécialisé dans le partage et la promotion de tutoriaux sur internet.

In this example, the TreeView control's dyamic loading functionality is explored. Dynamic loading of child nodes allows you to optmize performance by only loading data for and creating the nodes that will be visible when the tree is rendered.

Google Connection: Analyses et dépendances à « La Pieuvre » Décryptage de tous les services de Google

The purpose of this tutorial is to explain, step-by-step, how to create an AJAX desktop/homepage. The homepage we will create will have most of the capabilities of established homepages like Netvibes, PageFlakes, etc.

will give a simple example of how to setup BixData. It will hopefully be obvious how to adapt it to your situation. Although BixData is designed to handle large clusters of servers, I'll just show you how to maintain one. In this simple example I will assume you have a webserver and your own workstation. If the CPU usage on the webserver ever stays above 70% for 10 minutes you want Bix to restart apache and send you an email. If the webserver becomes unreachable you want to get an email. If the machine is still down after 1 hour you want to send an email to your coworker. All of this is very easy to set up with BixData.

This tutorial shows how to set up a two-node Apache web server cluster that provides high-availability. In front of the Apache cluster we create a load balancer that splits up incoming requests between the two Apache nodes. Because we do not want the load balancer to become another "Single Point Of Failure", we must provide high-availability for the load balancer, too. Therefore our load balancer will in fact consist out of two load balancer nodes that monitor each other using heartbeat, and if one load balancer fails, the other takes over silently

You have Linux installed and running. The GUI is working fine, but you are getting tired of changing your desktop themes. You keep seeing this "terminal" thing.

This tutorial shows how to configure a MySQL 5 cluster with three nodes: two storage nodes and one management node. This cluster is load-balanced by a high-availability load balancer that in fact has two nodes that use the Ultra Monkey package that provides heartbeat (for checking if the other node is still alive) and ldirectord (to split up the requests to the nodes of the MySQL cluster).

This tutorial provides step-by-step instructions on how to install Xen (version 2) on a Debian Sarge (3.1) system. It should apply to Ubuntu systems with little or no modifications.

This tutorial describes how to do automated server backups with the tool rdiff-backup. rdiff-backup lets you make backups over a network using SSH so that the data transfer is encrypted. The use of SSH makes rdiff-backup very secure because noone can read the data that is being transferred. rdiff-backup makes incremental backups, thus saving bandwidth.

tutorial xmlhttprequest

It is important that you specify the '-devel' part, otherwise you could end up with the Image_Graph-alpha version, which belongs to 'old' Image_Graph and has a completely different API!

A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses — like HTML pages, images and files (collectively known as representations) — for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again.