nguyenngochai hoasung01

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.

	- mình có 2 controllers khác nhau: users_controller và contact_details_controller
	- nhưng trong views/users/edit mình muốn thêm vào form new của contact_details thì hướng giải quyết ra sao nhỉ?
	- mình có tham khảo một số cách làm thì dùng form_tag url_for đến controllers và action name của contact_details_controller
	- nhưng hiện tại thì mình đã implement các action name cho mỗi controller xong hết rồi
	- sample code của mình:
	```
	class UserController < UserDashboardController
	include Devise::Controllers::Helpers
	include ContactDetailHelper
	before_action :authorize_resource

	require 'artoo'

	connection :arduino, :adaptor => :firmata, :port => '/dev/ttyACM0'
	device :led, :driver => :led, :pin => 13
	device :button, :driver => :button, :pin => 2

	work do
	on button, :push => proc {led.toggle}
	end

	It could be as simple as a stale PID file. It could be failing silently because your computer didn't complete the shutdown process completely which means postgres didn't delete the PID (process id) file. The PID file is used by postgres to make sure only one instance of the server is running at a time. So when it goes to start again, it fails because there is already a PID file which tells postgres that another instance of the server was started (even though it isn't running, it just didn't get to shutdown and delete the PID).

	To fix it remove/rename the PID file. Find the postgres data directory. On a MAC using homebrew it is /usr/local/var/postgres/, other systems it might be /usr/var/postgres/.
	To make sure this is the problem, look at the log file (server.log). On the last lines you will see: FATAL: lock file "postmaster.pid" already exists
	HINT: Is another postmaster (PID 347) running in data directory "/usr/local/var/postgres"?
	If so, rm postmaster.pid
	Restart your server. On a mac using launchctl (w

nguyenngochai hoasung01

Adding an audit log to your Rails app

nguyenngochai hoasung01