Intro

• USERNAME: the username on the server (ubuntu), for example “root”.
• SERVER.TLD: the server name, as you digit to connect in ssh, for example “host1.google.com”

Instructions

From your mac

ssh-keygen -t rsa -b 4096

• Enter file in which to save the key (/Users/LOCALUSER/.ssh/id_rsa): press enter
• Enter passphrase (empty for no passphrase):  enter the password you want to use
• Enter same passphrase again: enter again the password you want to use

3. in terminal copy and paste the command

scp ~/.ssh/id_rsa.pub USERNAME@SERVER.TLD:.ssh/authorized_keys

• USERNAME@SERVER.TLD’s password: digit current password for USERNAME on server SERVER.TLD

Conclusion

ssh USERNAME@SERVER.TLD

your mac will ask for the password that you inserted during the key creation and will store the key for the session (you will not asked for the password again until you turn off the computer).

Explanations (for nuts)

In step 2 you generate a key pair and you store it in your computer.
In step 3 you upload your public key to the server. You are saying “hello, here is my previous password. from now on I will authenticate using this key that I’m sending to you”. The server then will know to accept a login attempt that match the fingerprint of your key.
When later you try to connect to the server via ssh your computer (the mac) will try to send the fingerprint of your key to the server instead of the regular password and the server will accept it.

• No lower limits to credit purchase. The user can buy as few as 1 cent credit. Normally you would buy a few dollars or euros just to test the service.
• Sender ID fully customizable. You can send the SMS message from any sender with 11 alphanumeric characters, or 16 numeric characters.
• Lots of API to manage SMS sending from your application. Main API page here.
• Zend Framework library. The right Zend Framework library can be downloaded here.
• Real-time outgoing SMS report with status codes.
• Email to SMS feature.

Download

Prerequisites

• a working Zend Framework Project
• for these installation instructions: a default Zend Framework project with default directory structure

Installation

1. Copy the folder SmsGlobal contained in this archive in PROJECT/library/ (just where the directory Zend is, or other user libraries)
2. Open the application.ini file (PROJECT/application/configs/application.ini) and add this line in [production] section: autoloaderNamespaces[] = "SmsGlobal_"

Usage

$smsAdapter = new SmsGlobal_Sms_Adapter_Http('username', 'password');
$sms = new SmsGlobal_Sms($smsAdapter);
$sms->setOrigin('61447100250');
$sms->setIsTwoWay(false); //if true the Origin is ignored and sent from a special number
$sms->addDestination('61447100250')
    ->addDestination('61447100251')
    ->addDestination('61447100252');
$sms->setMessage('Test message');
$sms->send();

I test

Primo test: dal cliente NGI-Eolo al server NGI-Eolo (rete interna NGI)

Test effettuato il 15/12/2011 con collegamento al server di test http://test.ngi.it

Secondo test: dal cliente NGI-Eolo al resto di internet (youtube, facebook, google, …)

Test effettauto il 15/12/2011 con l’ausilio dello script di http://www.speedtest.net con selezione di tutti i siti di test italiani (Vodafone, diverse università, …)

Conclusioni

 Aggiornamento

Requisiti

• server con installato Mercurial (in questo articolo trattiamo l’uso di un server linux tipo debian, come ubuntu, ma è possibile usare anche un server windows opportunamente configurato). Per l’istallazione di Mercurial cliccate qui.
• workstation con installato Mercurial (leggi le istruzioni per installare Mercurial nella tua workstation)

Creare il repository Mercurial nella macchina locale

~$ cd workspace/project/
~/workspace/project$

~/workspace/project$ ls -a
. .. index.php  test.php  test.thml  test.txt

$ hg init .

~/workspace/project$ ls -a
.  ..  .hg  index.php  test.php  test.thml  test.txt

~/workspace/project$ hg summary
genitore: -1:000000000000 tip (repository vuoto)
branch: default
commit: 4 sconosciuti (pulito)
update: (aggiornato)

~/workspace/project$ hg add
aggiunta in corso di index.php
aggiunta in corso di test.php
aggiunta in corso di test.thml
aggiunta in corso di test.txt
~/workspace/project$ hg commit -u nome-utente -m "Custom message, first commit."
~/workspace/project$

~/workspace/project$ hg summary
genitore: 0:67329e405264 tip
 Custom message, first commit.
branch: default
commit: (pulito)
update: (aggiornato)

Creare il repository Mercurial nel server

$ ssh root@server
root@server's password:
...
root@server:~# cd /var/www/project

# hg init .

# cd .hg
# vi hgrc

[hooks]
# update working directory after adding changesets
changegroup.update = hg update

Inviare le modifiche al server

$ hg push ssh://root@server//var/www/project

Prassi per l’upload

$ hg add
$ hg commit -u nome-utente -m "messaggio di commit"
$ hg push ssh://root@server//var/www/project

• In modern web design concept, the layout of the page is entirely CSS based.
• The CSS is rendered in a slightly differen way in every browser
• When sending the code to the browser, we know wich browser is from the header request or – alternatively – the javascript running at client side knows it.

I am trying to make new website and I would like to know how to make it compatible with cross-browser as now I am able to view my website perfectly with Google chrome and when I see the same with Firefox 7.0 it’s looking very ugly and with IE 8 its looking better.So I would like to know how to make compatible. Any suggestions will be greatly appreciated!

• Gradatamente sparisce la connessione dal client connesso a NGI Eolo con alcuni siti internet di rilevanza internazionale (Facebook, Twitter, …) ma resta la connessione con altri siti locali. Alla fine si resta collegati solo con server presenti nella webfarm Inet di Settimo Milanese (o almeno dei pochi server con i quali si riesce ancora a collegasi, senz’altro ci sono tutti quelli che a mia conoscenza si trovano in questa webfarm).
• Contemporaneamente però i server presenti nella webfarm Inet comunicano correttamente con il resto del mondo.

1. si fa un ping a facebook.com -> non raggiungibile
2. si fa un ping a un server nella webfarm Inet (ad esempio fite.it) -> raggiungibile
3. ci si collega via ssh a un server nella webfarm inet
4. dal server si fa un ping a facebook.com -> raggiugibile