Linux SSH - Limit user access to a specific directory

Make sure you are the SuperUser.


Create a user, by typing this command and following the process

adduser username

Specify user base directory to the directory you want

usermod --home /var/www username

If you want a group of users to only access this directory, add the user to a group

addgroup mygroup

usermod -g mygroup username 

Now, specify the directory to be exclusive. Go to "/etc/ssh" and type

nano sshd_config

Find and comment (# at the beginning) this line

Subsystem sftp /usr/lib/openssh/sftp-server

And write this

Subsystem sftp internal-sftp

Match group mygroup

    ChrootDirectory /var/www/

    X11Forwarding no

    AllowTcpForwarding no

    X11Forwarding no  

    ForceCommand internal-sftp

That's all, have fun.

HW[RG²] Marketing design pattern for interactive campaigns

Hello,

It is by creating and involving a photo/video capture application in full html5, specially designed to work on All In One computers, during prestigious companies events, that I've got a revelation.

I'm coding an interactive application that the user can interact with to share a content (photo or video) with his world. Of course, we collect user datas with his authorization, like any other interactive marketing campaign available.

The fact is that, I've noticed that everytime we have to deliver an application, we still brainstorming about the user journey, trying to improve the previous version.
And, we are not isolated case, many other marketing professionals and ux designers still doing the same.

This is why, I'm bringing the HW[RG²] design pattern for marketing interactive campaigns.


HW[RG²] stand for:
- Hello
- Who is
- Ready
- Go
- Realize
- Get

These acronyms are steps a user has to go through in your application to live the experience you want him to live.
You can traduce these steps more fluidly like that: "Hello! Who is ready to go, realize and get.".


What does each of these steps mean?

Hello
Main page, that informs the user and invites him to participate.

Who is?
Page that let user fills his personal informations in order to participate (this page can be integrated in the previous step).

Ready
This page prepares the user to do the required action.

Go
This page does the main action (content production).

Realize
This page summarizes the content produced by the user, and invites him to restart or valid.

Get
This page valids the produced content, thanks the user and can do a further action, like print, email etc... 


You're in, this is the HW[RG²] design pattern.