Personal tools

December

Dec 29, 2011

Plone in 10 secondi

Ho provato per voi il nuovo servizio creato da Alan Runyan per creare al volo il tuo Plone site.

Impiegherò sicuramente più tempo a raccontarti come farlo che quello che ho utilizzato per creare massimoazzolini.ploud.com.

Configura

Il sistema è molto semplice e molto
come-te-lo-aspetti:

  1. vai su ploud.com
  2. iscriviti: email, dominio, lingua
  3. controlla la tua posta: c'è una mail di validazione con un link (devo davvero dirti che fare? :-)
  4. ti chiederà la password che vorrai utilizzare
  5. fatto.

Ci sono 2 tipi di servizi: gratuito e a canone mensile. Fondamentalmente si tratta della stessa soluzione, ma a pagamento ottieni:

  • la possibilità di avere un tuo dominio
  • più banda
  • più spazio
  • indicizzazione di google

Scegli il tema

Ora puoi impostarti il tuo tema tra quelli disponibili.

Il tema sceltoTra gli 11 disponibili, io ho scelto "Earthling two" che avevamo adattato e rilasciato mesi fa su pypi.
E' bello vedere come ancora una volta la comunità funziona.

Tra l'altro l'uso di Diazo facilita molto l'implementazione di questo tipo di servizi: oggi ci sono "solo" 11 temi, ma è possibile aggiungerne altri.

Aggiungi funzionalità

Ora puoi aggiungere gli add-on, tra cui:

  • Carousel
  • Dropdown menu
  • Autenticazione con OpenID
  • PloneFormGen per creare moduli online
  • Simple Social: vuoi farti mancare Facebook & co?
  • Workflow personalizzati per cartella
  • Copia di lavoro
  • plone.app.caching: cache per siti più veloci

e i due nuovi cavalli di razza di Plone:

  • Dexterity
  • Diazo theme support

Quindi?

Beh, è Plone! Hai tutto quello che puoi fare con Plone, niente di meno. Ci sono alcuni add-on interessanti anche se c'è tutta una serie di ulteriori add-on che vorrei già poter usare.

L'attuale target di mercato è sicuramente molto basico e i temi sono veramente pochi (anche se con Diazo e un po' di olio di gomito puoi fare faville).

Seconde me ha le potenzialità necessarie per crescere. Stay tuned.

Dec 21, 2011

Plone SEO? collective.perseo!

Filed Under:

The package collective.perseo has just been released. collective.perseo is a package for Search Engine Optimization and offers several kind of SEO features

why collective.perseo?

collective.perseo was born during a collaboration with Irene Capatti, Federica D'Elia and SEO Specialist Andrea Pernici. The product quintagroup.seoptimaizer is very useful, but Andrea needed something more.

Features

New package for Search Engine Optimization (SEO)

With collective.perseo you can manage:

  • globally (configurations applied to each page of the site), through “PerSEO” tool under Add-on Configuration:

    • Webmaster Tools (Google Webmaster Tools, Yahoo Site Explorer, Bing Webmaster Tools)

    • tag title, description and keywords meta tags, separately for:

      • Home page

      • Single pagePerSEO title

      • Search page

      • Not Found page

      • Author page

      • Site Map page

      • Contact page

      • Event

      • File

      • Folder

      • Image

      • Link

      • News Item

      • Topic

    • Disable the indexing of resources using noindex and nofollow, separately for:

      • Search page

      • Login and Registration pages

      • Administration pages

      • Single pages

      • Event

      • File

      • Folder

      • Image

      • Link

      • News Item

      • Topic

      • (also handle noodp, noydir, noarchive, nosnippet)

    • Content types included in the sitemap.xml.gzPerSEO site map

    • Ping sites (Google, Bing, Ask) automatically when the Site Map is updated

    • Indexing RSS feeds

    • Add itemscope and itemtype attributes to body tag (if you install the extension collective.perseoschema for Schema.org)

  • one by one, through “SEO” tab on each content of the site (allows you to change SEO settings for that specific content):

    • tag title and description and Keywords meta tags

    • Meta Robots Follow Tag (follow/nofollow)

    • Meta Robots Index Tag (index/noindex)

    • Meta Robots Advanced Tag (noodp, noydir, noarchive, nosnippet)

    • Canonical URL

    • Content included in the sitemap.xml.gz (yes/no).

    • Priority of content in sitemap.xml.gz

    • itemtype attribute (if you install the extension collective.perseoschema for Schema.org)

PerSEO tab

Useful links

http://pypi.python.org/pypi/collective.perseo

http://pypi.python.org/pypi/collective.perseoschema

http://plone.org/products/collective.perseo

http://plone.org/products/collective.perseoschema

Dec 06, 2011

SSH tips and tricks: how to save time configuring properly SSH

Filed Under:

This blog post is about ssh client configuration. Configuring ssh is a really good practice both for saving time and keeping organized your connections data. Even though the blogosphere is full of posts like this, I think it is worth repeating because the practice of keeping an up to date ssh configuration is not so diffused.

In my daily activity I find myself connecting to a lot of servers and it is hard to remember for each of them the correct hostname or IP and the related credentials.

To speed up my work I try to keep has much as possible updated my .ssh/config file.

Let's say, for example that one of our clients, let's say ACME :), gives us access to a fictitious server with the IP address 999.999.999.999. 

They give us the access that server with the username bugs and ssh is listen to port 2222.

As soon as I am authorized to connect to a new server I insert a new section to the file like this:

# The new acme server
Host acme
HostName 999.999.999.999
Port 2222
User bugs

 This way instead of typing:

ssh -p2222 bugs@999.999.999.999

I can just type:

ssh acme

with the same effects.

The benefits of that go beyond the use of ssh, because the same configuration file has effect on other ssh related programs like scp, rsync and sshfs.

In addition .ssh/config is parsed by bash completion scripts so I can save further keystrokes (holy laziness)!

This is good, more than for today, for tomorrow because time passes and I can forget the username, the server IP or the port, but I would hardly forget I worked for ACME and to get those info quickly reading .ssh/config is enough.

Of course I can add many hosts sections to the .ssh/config like I am showing in this example:

## List of ACME servers ##
# The staging server
Host acme-staging
HostName staging.example.com
User bugs
# The production server
Host acme-production
HostName production.example.com
User bunny

## Another customer ##
Host demo
HostName 10.0.1.100
User donald

# I can also setup a tunnel to a port
Host demo-debug
HostName 10.0.1.100
User root
LocalForward 8080 localhost:8080

As you can see each section starts with the Host declaration and the settings are effective only for that specific Host.

In the last example we make a tunnel forwarding the 8080 port to localhost, useful in case the server firewall filters direct connections from outside.

With this configuration the command:

ssh demo-debug

is equivalent to:

ssh root@10.0.1.100 -L 8080:localhost:8080

 

Further readings

Beyond the nice manual page about ssh configuration:

man ssh_config

you could find very useful those links to

A note to KDE users

I found out that also sftp and fish KIO slaves are aware of ssh configuration, with the difference that fish overrides the User directive, i.e., using the example before, to connect to the acme server as bugs I have to point dolphin to either fish://bugs@acme or to sftp://acme

.