Andrey Kozlovskiy cfc1020

Sessions and Conversations

HTTP is a stateless protocol. Sessions allow us to chain multiple requests together into a conversation between client and server.

Sessions should be an option of last resort. If there's no where else that the data can possibly go to achieve the desired functionality, only then should it be stored in the session. Sessions can be vulnerable to security threats from third parties, malicious users, and can cause scaling problems.

That doesn't mean we can't use sessions, but we should only use them where necessary.

	# Manually secure port 6379
	sudo iptables -A INPUT -p tcp --dport 6379 -s xxx.xxx.xxx.xxx -j ACCEPT
	sudo iptables -A INPUT -p tcp --dport 6379 -j DROP
	sudo iptables -L

	# Save current firewall config
	sudo iptables-save > /etc/iptables.conf

	# Load iptables.conf on startup
	sudo nano /etc/rc.local

	So i was using Rails 4.1 with Unicorn v4.8.2 and when i tried to deploy my app it doesn't start properly and into the unicorn.log file i found this error message:

	"app error: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml` (RuntimeError)"

	After a little research i found that Rails 4.1 change the way to manage the secret_key, so if we read the secrets.yml file located at exampleRailsProject/config/secrets.yml (you need to replace "exampleRailsProject" for your project name) you will find something like this:

	# Do not keep production secrets in the repository,
	# instead read values from the environment.
	production:
	secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>

	<VirtualHost *:80>
	ServerName example.com
	ServerAlias *.example.com
	DocumentRoot /rails_app_directory/public

	# Redirect all requests that don't match a file on disk under DocumentRoot get proxied to Puma
	RewriteEngine On

	<Proxy balancer://unicornservers>
	BalancerMember http://127.0.0.1:5100

Andrey Kozlovskiy cfc1020

Sessions and Conversations

Adding, Accessing, and Removing Data