Hash Train - Home

Why we create Teaser 1-2-3

2008-08-05T10:03:00Z

Our service is working openly only two days. As we expected, the project is getting different attention— somebody greets, somebody doesn’t trust. So, why have we done Teaser 1-2-3?

As we said in previous article, we’ve done it for our own needs, exactly for a one of our projects: EstateHQ (Estate headquarters).

The true is that The Headquarters is not only project we planned, so, there will be other “teaser” projects. And it was a good idea to take out the teaser page code into individual service. The service with comfortable interface makes “teaser routine”.

The principle of Teaser 1-2-3 allows using a HTML support only on server with teaser page :) You make minimally two pages: the first one with the form of registration generated by Teaser 1-2-3, and the second one welcomes user after his successful registration— with your thanks for passed e-mail. This technical feature could be useful for you if your project server is not fully set up yet.

So, then we decided to share the service with other developers for free.

Ask your questions and exchange experiences at the support group, it’s address http://groups.google.com/group/teaser123

Teaser 1-2-3 is absolutely free. Your respect, if our service helps you economize your time and concentrate on your project, is the only payment for us.

Have a nice work!

Teaser 1-2-3. Free service for web-developers

2008-08-05T09:56:00Z

The creation of any new project is some stages way, and one of the stages is announcing of the project with help of teaser page— you just lift the veil of mystery and declare forthcoming opening of a new service.

So, collecting of e-mails on the teaser page is a classic way. You can and had to tell all that persons about every stage of development, to invite them for the opening; their interest is very important thing for you, as a matter of fact they are your first and probably the most loyal users!

Background

Have you read Getting Real? There was mention about stage of the collecting of e-mails on the teaser page.

So, this is not a problem. But it could be a technical problem if you planning one or more new projects. We made this product for our own needs— to solve this task (collecting of e-mails and comfortable work with it). Then we decided to share it with other developers, and Teaser 1-2-3 was created.

Features

The main function— collecting and management of e-mails of all persons registered on a teaser page. Teaser 1-2-3 allows generation of a special code for placing it on the teaser page to get a registration form.

When user fill the form and sent you e-mail, Teaser 1-2-3 save this e-mail and redirect the user to the page “Thank you for your registration” (the page address you point at your profile).

Besides, after saving of e-mail Teaser 1-2-3 sends “welcome” letter, with text made by your own.

At the user profile Teaser 1-2-3 you can manage e-mails list; after “teaser” stage you can export this list into CSV format to use it in future.

Pleasant detail— Teaser 1-2-3 remember address, where is user came to your teaser page from.

Resume

Keep an eye on our blog, to know all renovations of the Teaser 1-2-3. The most comfortable way is to do it by feed

Ask your questions at support group

Have a pleasant work!

Rails and SSL

2008-04-27T12:41:00Z

Sometimes it’s necessary to encrypt traffic from some parts of site. Thereto you had to use HTTPS protocol. HTTPS is widely used all over the WEB world in applications demanding safe connecting, for example, in payment systems.

Rails developers confront by some problem: Mongrel and Webrick are not support SSL encription.

A quotation from Mongrel FAQ:

Does Mongrel support SSL? No, it isn’t efficiently to make SSL encription support in Ruby web-server because you can use any of popular web-servers, if would work faster.

Web-server setup

Apache

<VirtualHost *:80>
   ServerName localhost
   ServerAlias 127.0.0.1

   ProxyPass / http://localhost:3000/
   ProxyPassReverse / http://localhost:3000
   ProxyPreserveHost on
</VirtualHost>

<VirtualHost *:443>
    SSLEngine On
    ServerName localhost
    ServerAlias 127.0.0.1

    ProxyPass / http://localhost:3000/
    ProxyPassReverse / http://localhost:3000
    ProxyPreserveHost on

    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
    SSLCertificateFile "/etc/httpd/ssl/mysite.crt"
    SSLCertificateKeyFile "/etc/httpd/ssl/mysite.key"

    # Установите X-FORWARDED_PROTO для работы с ssl_requirement плагином
    RequestHeader set X_FORWARDED_PROTO 'https'
</VirtualHost>

Our advice: Use Apache 2.x.x and higher to avoid great number of problems.

nginx

server {
  listen 443;
  ssl on;

  # ssl сертификат
  ssl_certificate /etc/nginx/certs/server.crt; 
  # ssl ключ
  ssl_certificate_key /etc/nginx/certs/server.key; 

  location / {
     # Установите X-FORWARDED_PROTO для работы с ssl_requirement плагином
     proxy_set_header X-FORWARDED_PROTO https;
  }
}

Plugin

Use plugin SSL Requirement for comfortable work with HTTPS connection.

class ApplicationController < ActiveRecord::Base
    include SslRequirement
end

class AccountController < ApplicationController
    ssl_required :signup, :payment
    ssl_allowed :index

    def signup
      # Non-SSL access will be redirected to SSL
    end

    def payment
      # Non-SSL access will be redirected to SSL
    end

    def index
      # This action will work either with or without SSL
    end

    def other
      # SSL access will be redirected to non-SSL
    end
  end

Have a nice work!