#!/bin/bash
echo "Buscando mail de: $1"
for i in $(grep sasl_username=$1 /var/log/maillog | awk '{print $6}'| cut -c -12); do grep $i /var/log/maillog| grep -E "from=|to="|awk '{if ($7 ~ "from"){ print "\n" $7 }else if ($7 ~ "to"){print $7}}';done
Digging about another project that requires sending messages via D-Bus I decided to make this simple app, that shows a notification of my recent tweets (your) timeline , and with this I can be updated about what's going on twitter while you do your daily tasks ...
It was originally madeonly for Linux environments, because in my work I have ubuntu, but then with the help of @dual3nigma decided port to mac and window$ using growl.
The app requires the libnotify library for Linux environments and growl for Mac / Window$, was made with Node.js and the code is available at Github where you will find all the steps to install and use.
Indagando sobre otro proyecto que requiere envio de mensajes a través de D-Bus se me ocurrió hacer esta simple app, que me mustra en un cuadro de notificación los últimos tweets de mi (tu) timeline, y con esto poder estar actualizado de lo que pasa en twitter al mismo tiempo que haces tus tareas diarias...
En un principio fue realizada sólo para entornos linux, ya que en mi trabajo tengo ubuntu, pero luego con la ayuda de @dual3nigma decidí portalo a mac y window$ utilizando growl.
La app require de la librería libnotify en entornos linux y de growl para Mac / Window$, fue realizada con Node.js y el código está disponible en Github en donde encontrará todos los pasos para instalarla y usarla.
app.get('/',function(req,res){
res.write('handler : / \n');
res.end();
});
Vemos que responde a los dos requerimientos, ya que express se encarga de esa última barra (/) por nosotros.lucaMac:02-Routes pepo$ curl localhost:3000 handler : / lucaMac:02-Routes pepo$ curl localhost:3000/ handler : /
app.get('/users/:id?',function(req,res){
res.write('handler: /users/:id? \n');
res.write('parametros: \n');
for(key in req.params){
res.write('\t'+key+' : '+req.params[key]);
}
res.write('\n');
res.end();
});
También podemos definir varios placeholders simplemente cambiando el primer argumento:lucaMac:02-Routes pepo$ curl localhost:3000/users handler: /users/:id? parametros: id : undefined lucaMac:02-Routes pepo$ curl localhost:3000/users/pedro handler: /users/:id? parametros: id : pedro lucaMac:02-Routes pepo$ curl localhost:3000/users/25 handler: /users/:id? parametros: id : 25
app.get('/users/:id/:action',function(req,res){
res.write('handler: /users/:id \n');
res.write('parametros: \n');
for(key in req.params){
res.write('\t'+key+' : '+req.params[key]+'\n');
}
res.end();
});
app.get('/users/:id([0-9]+)/:action(edit|delete|create)',function(req,res){
res.write('handler: /users/:id \n');
res.write('parametros: \n');
for(key in req.params){
res.write('\t'+key+' : '+req.params[key]+'\n');
}
res.end();
});
Como vemos funciona y si la regex no se cumple 404 no se puede encontrar....curl localhost:3000/users/25/edit handler: /users/:id parametros: id : 25 action : edit lucaMac:02-Routes pepo$ curl localhost:3000/users/25/delete handler: /users/:id parametros: id : 25 action : delete lucaMac:02-Routes pepo$ curl localhost:3000/users/25/del Cannot GET /users/25/del lucaMac:02-Routes pepo$ curl localhost:3000/users/pedro/delete Cannot GET /users/pedro/delete
* Ya veremos al final una posibilidad de manejar esto de una forma más prolucaMac:02-Routes pepo$ curl localhost:3000/users/pedro/delete -I HTTP/1.1 404 Not Found X-Powered-By: Express Content-Type: text/plain Connection: keep-alive
app.post('/users',function(req,res){
res.write('handler post: /users/ \n');
res.write('parametros en body: \n');
for(key in req.body){
res.write('\t'+key+' : '+req.body[key]+'\n');
}
res.end();
});
/* post */
app.post('/users',function(req,res){
res.write('handler post: /users/ \n');
res.write('parametros en body: \n');
for(key in req.body){
res.write('\t'+key+' : '+req.body[key]+'\n');
}
res.end();
});
/* We can use put to be more semantics, like a RESTful api.
For this be use the middleware methodOverride, this
middleware check for the input _method in the body
(this input could be hidden for don't show to the
end user), and if its present tranform the post in the
_method input value and don't pass this in req.body
*/
app.put('/users',function(req,res){
res.write('handler put: /users/ \n');
res.write('parametros en body: \n');
for(key in req.body){
res.write('\t'+key+' : '+req.body[key]+'\n');
}
res.end();
});
/* delete, as in put we can use methodOverride to be
more semantic
*/
app.delete('/users',function(req,res){
res.write('handler delete: /users/ \n');
res.write('parametros en body: \n');
for(key in req.body){
res.write('\t'+key+' : '+req.body[key]+'\n');
}
res.end();
});
Un post, pero que será respondido como put:lucaMac:02-Routes pepo$ curl -X POST -d "id=32&action=delete" localhost:3000/users/ handler post: /users/ parametros en body: id : 32 action : delete
vean como se pasa el valor de _method para que el middleware sobreescriba el métodolucaMac:02-Routes pepo$ curl -X POST -d "id=32&action=delete&_method=put" localhost:3000/users/ handler put: /users/ parametros en body: id : 32 action : delete
Y con esto queda explicado el middleware...lucaMac:02-Routes pepo$ curl -X POST -d "id=32&action=delete&_method=delete" localhost:3000/users/ handler delete: /users/ parametros en body: id : 32 action : delete
app.all('*',function(req,res){
res.write('handler all: *\n');
res.write('ERR, no regex match\n');
res.end();
});
lucaMac:02-Routes pepo$ curl -X POST -d "id=32&action=delete" localhost:3000/users/dasdsdas handler all: * ERR, no regex match lucaMac:02-Routes pepo$ curl -X GET -d "id=32&action=delete" localhost:3000/usedasd handler all: * ERR, no regex match
I will explain each directory use:pepo@frank3:~$ mkdir 01-basic_express && cd 01-basic_express pepo@frank3:~$ mkdir views pepo@frank3:~$ mkdir node_modules pepo@frank3:~$ mkdir -p public/img pepo@frank3:~$ mkdir -p public/css pepo@frank3:~$ mkdir -p public/js
views : The directory where our templates lives
node_modules : Where were installed modules it will use
public : Content css, js, imagenes,etc.
/**
* Module dependencies.
*/
var express = require('express');
var app = module.exports = express.createServer();
// Configuration
app.configure(function(){
app.set('views', __dirname + '/views');
app.set('view engine', 'ejs');
app.set('view options', {
layout: false
});
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(app.router);
app.use(express.static(__dirname + '/public'));
});
app.configure('development', function(){
app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
});
// Routes
app.get('/',function(req,res){
res.render("index",{
title: "01 - basic express ",
banner: "Hello from template!"
});
});
app.listen(3000);
console.log("Express server listening on port %d in %s mode", app.address().port, app.settings.env);
var express = require('express');
var app = module.exports = express.createServer();
// Configuration
app.configure(function(){
app.set('views', __dirname + '/views');
app.set('view engine', 'ejs');
app.set('view options', {
layout: false
});
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(app.router);
app.use(express.static(__dirname + '/public'));
});
That will allow us to access the post as follows:<form action="/" method="post"> <input name="_method" type="hidden" value="put" /> <input name="user[name]" type="text" /> <input type="submit" value="Submit" /> </form>
app.put('/', function(){
console.log(req.body.user);
});
Yes, I had read the news that they had exploited a vulnerability that allowed update rails attributes inserting a new SSH key for more detail can read these links [0].
lucaMac:nodeapps pepo$ git clone git@github.com:pepoviola/Socket.IO_rooms.git
Cloning into Socket.IO_rooms...
ERROR: Hi pepoviola, it's GitHub. We're doing an SSH key audit.
Please visit https://github.com/settings/ssh/audit/1767330
to approve this key so we know it's safe.
Fingerprint: 7c:(...):54
fatal: The remote end hung up unexpectedly
ssh-keygen -lf ~/.ssh/id_rsa.pubWhich we will return three fields, the first is the size, the second is our fingerprint and is ultimately the public key file.
2048 7c: (...): 54 /Users/pepo/.ssh/id_rsa.pub (RSA)
Así es, había leido de la noticia de que habían explotado una vulnerabilidad de rails que permitía updetear los atributos insertando una nueva key de SSH, para más detalle puede leer estos links [0].
lucaMac:nodeapps pepo$ git clone git@github.com:pepoviola/Socket.IO_rooms.git
Cloning into Socket.IO_rooms...
ERROR: Hi pepoviola, it's GitHub. We're doing an SSH key audit.
Please visit https://github.com/settings/ssh/audit/1767330
to approve this key so we know it's safe.
Fingerprint: 7c:(...):54
fatal: The remote end hung up unexpectedly
ssh-keygen -lf ~/.ssh/id_rsa.pubEl cual nos devolverá tres campos, el primero es el tamaño, el segundo es nuestro fingerprint y por último es archivo de la clave pública.
2048 7c:(...):54 /Users/pepo/.ssh/id_rsa.pub (RSA)
pepo@frank3:~$ mkdir 01-basic_express && cd 01-basic_express pepo@frank3:~$ mkdir views pepo@frank3:~$ mkdir node_modules pepo@frank3:~$ mkdir -p public/img pepo@frank3:~$ mkdir -p public/css pepo@frank3:~$ mkdir -p public/js
views : Es el directorio donde alojaremos nuestros templates
node_modules : Donde se instalaran los módules que utilizaremos
public : Directorio de contenido, aquí alojaremos nuestros css, js, imagenes, etc.
/**
* Module dependencies.
*/
var express = require('express');
var app = module.exports = express.createServer();
// Configuration
app.configure(function(){
app.set('views', __dirname + '/views');
app.set('view engine', 'ejs');
app.set('view options', {
layout: false
});
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(app.router);
app.use(express.static(__dirname + '/public'));
});
app.configure('development', function(){
app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
});
// Routes
app.get('/',function(req,res){
res.render("index",{
title: "01 - basic express ",
banner: "Hello from template!"
});
});
app.listen(3000);
console.log("Express server listening on port %d in %s mode", app.address().port, app.settings.env);
var express = require('express');
var app = module.exports = express.createServer();
// Configuration
app.configure(function(){
app.set('views', __dirname + '/views');
app.set('view engine', 'ejs');
app.set('view options', {
layout: false
});
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(app.router);
app.use(express.static(__dirname + '/public'));
});
Que nos permitirá acceder al post de la siguiente forma:<form action="/" method="post"> <input name="_method" type="hidden" value="put" /> <input name="user[name]" type="text" /> <input type="submit" value="Submit" /> </form>
app.put('/', function(){
console.log(req.body.user);
});
lucaMac:BLOG_POSTs pepo$ node
> var Client = require('mysql').Client
Error: Cannot find module 'mysql'
at Function._resolveFilename (module.js:332:11)
at Function._load (module.js:279:25)
at Module.require (module.js:354:17)
at require (module.js:370:17)
at repl:1:14
at REPLServer.eval (repl.js:80:21)
at repl.js:190:20
at REPLServer.eval (repl.js:87:5)
at Interface. (repl.js:182:12)
at Interface.emit (events.js:67:17)
>
If fails, proceed to install the module via npm:var Client = require('mysql').Client,
client = new Client();
client.user = 'user';
client.password = 'password';
client.host='127.0.0.1';
client.port='3306';
client.database='database_name'
client.connect();
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
client.query(
"select * from table where campo1 > 1 limit 10;",
function select(err, results, fields) {
if (err) {
console.log("Error: " + err.message);
throw err;
}
console.log("Number of rows: "+results.length);
console.log(results);
for (var i in results){
var result = results[i];
res.write(result.campo1+"\n");
}
res.end();
});
}).listen(1337, "0.0.0.0");
console.log('Server running ');
var Client = require('mysql').Client,
client = new Client();
client.user = 'user';
client.password = 'password';
client.host='127.0.0.1';
client.port='3306';
client.database='DB'
client.connect();
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
client.query(
"select * from table where campo1 > 1 limit 10;",
function select(err, results, fields) {
if (err) {
console.log("Error: " + err.message);
throw err;
}
console.log("Number of rows: "+results.length);
console.log(results);
res.write(results);
for (var i in results){
var result = results[i];
res.write(result.campo1+"\n");
}
res.end();
});
}).listen(1337, "0.0.0.0");
console.log('Server running ');
* the last step as root Once installed, continue with the installation of modules. For this node has npm (which is Node Package Manager) that allows us to install the modules with a single command install npm./configure make make install *
curl http://npmjs.org/install.sh | shand within it begin to install the modules you require. This is important because when you install the modules npm node_modules create the directory (if not there before), and install the modules in that directory.cd "path to nodeapps"
var sys = require('sys');
Once unpacked and could start the service mongod and start, but I'd rather create the directory structure I will use my base, create two directories for data and logs, the first store the files of the database and the second of logs. I also create the configuration file with which I will start the service, in my case is as follows:
pepo@sokol:~/DESARROLLO/POSTS/node_socket_mongo$ wget http://fastdl.mongodb.org/linux/mongodb-linux-i686-2.0.2.tgz
2012-02-28 11:42:19 (1.06 MB/s) - `mongodb-linux-i686-2.0.2.tgz' saved [38157227/38157227]
pepo@sokol:~/DESARROLLO/POSTS/node_socket_mongo$ tar -xzf mongodb-linux-i686-2.0.2.tgz
Bind_ip option is set to only listen on localhost requests (since by default it does on all interfaces) and indicate that we will not configure the authentication and verbose.cat mongod.config dbpath = /home/pepo/nodeapps/data/ logpath =/home/pepo/nodeapps/logs/mongodb.log bind_ip = 127.0.0.1 noauth = true verbose = true
* Inside the unzipped directory MongoDBbin/mongod --config mongod.config *
# mongodb-linux-i686-2.0.2/bin/mongod --config mongod.config
all output going to: ./logs/mongodb.log
Well, with this we have our environment set up and configured to start programming applications in node.js with MongoDB, but that will be for the next post....pepo@sokol:bin$ ./mongo MongoDB shell version: 2.0.2 connecting to: test > show dbs local (empty)
* este último como root./configure make make install *
curl http://npmjs.org/install.sh | shy dentro de él comienzo a instalar los modulos que requiero. Esto es importante porque al instalar los modulos npm creará el directorio node_modules (siempre y cuando no exista antes), e instalará los modulos en dicho directorio.cd "path to nodeapps"
var sys = require('sys');
Una vez descomprimido ya podríamos arrancar el servicio mongod y comenzar, pero antes prefiero crear la estructura de directorios que utilizaré con mi base, para eso creo dos directorios data y logs, el primero guardará los archivos de la base de datos y el segundo los archivos de logs. También creo el archivo de configuración con el que voy a levantar el servicio, en mi caso tiene la siguiente forma:
pepo@sokol:~/DESARROLLO/POSTS/node_socket_mongo$ wget http://fastdl.mongodb.org/linux/mongodb-linux-i686-2.0.2.tgz
2012-02-28 11:42:19 (1.06 MB/s) - `mongodb-linux-i686-2.0.2.tgz' saved [38157227/38157227]
pepo@sokol:~/DESARROLLO/POSTS/node_socket_mongo$ tar -xzf mongodb-linux-i686-2.0.2.tgz
La opción bind_ip está configurada para que sólo escuche las peticiones sobre el localhost (ya que por defecto lo hace sobre todas las interfaces) e indicamos que no tendremos autenticación y configuramos el verbose.cat mongod.config dbpath = /home/pepo/nodeapps/data/ logpath =/home/pepo/nodeapps/logs/mongodb.log bind_ip = 127.0.0.1 noauth = true verbose = true
* Dentro de directorio descomprimido de mongoDBbin/mongod --config mongod.config *
# mongodb-linux-i686-2.0.2/bin/mongod --config mongod.config
all output going to: ./logs/mongodb.log
Bueno, y con esto ya tenemos nnuestro entorno instalado y configurado para comenzar a programar aplicaciones en con node.js con mongoDB, pero eso quedará para la próxima....pepo@sokol:bin$ ./mongo MongoDB shell version: 2.0.2 connecting to: test > show dbs local (empty)