Andrej Antas redrick

Adding an audit log to your Rails app

If you have any sort of administrative interface on your web site, you can easily imagine an intruder gaining access and mucking about. How do you know the extent of the damage? Adding an audit log to your app is one quick solution. An audit log should record a few things:

controller entry points with parameter values
permanent information about the user, like user_id
transient information about the user, like IP and user_agent

Using the Rails framework, this is as simple as adding a before_action to your admin controllers. Here’s a basic version that I’m using in production.

Commands examples

If the namespace is not used then the commands will perform on top of the default database. bundle exec rake db:create bundle exec rake db:migrate

By using the namespace we are going to use all the configuration for our alternate DB. bundle exec rake store:db:create bundle exec rake store:db:migrate

	#Model

	expect(@user).to have(1).error_on(:username) # Checks whether there is an error in username
	expect(@user.errors[:username]).to include("can't be blank") # check for the error message

	#Rendering
	expect(response).to render_template(:index)

	#Redirecting
	expect(response).to redirect_to(movies_path)

	# GNU Screen - main configuration file
	# All other .screenrc files will source this file to inherit settings.
	# Author: Christian Wills - [email protected]
	shell -$SHELL

	# Allow bold colors - necessary for some reason
	attrcolor b ".I"

	# Tell screen how to set colors. AB = background, AF=foreground
	termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'

	cd ~
	sudo yum update
	sudo yum install java-1.7.0-openjdk -y

	wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.90.5.tar.gz -O elasticsearch.tar.gz

	tar -xf elasticsearch.tar.gz
	rm elasticsearch.tar.gz
	mv elasticsearch-* elasticsearch
	sudo mv elasticsearch /usr/local/share