Shoaib Malik shoaibmalik786

Audit Report

controllers are not covered with rspecs
gem 'simplecov' is added in Gemfile but is not correctly implemented and it is not generating the html file to check the specs coverage.

Query should not be written on views. check on app/views/component/gupdates_index/_index.html.erb
There is an examples controller which is of no use, we should not keep the redundant code.
provide_names_and_ids method is not being used anywhere in the code which is defined in concern inside model

	### Install OpenJDK
	cd ~
	sudo apt-get update
	sudo apt-get install openjdk-7-jre-headless -y

	### Download and Install ElasticSearch
	### Check http://www.elasticsearch.org/download/ for latest version of ElasticSearch and replace wget link below
	wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.4.3.deb
	sudo dpkg -i elasticsearch-1.4.3.deb


	MANAGE SERVER WITH PUTTY
	- Once you setup your amazon server and get an amazon instance, you should have a private key private_key.pem
	- Open puttygen
	- Browse private_key.pem
	- Generate .ppk file
	- Open Putty
	- Enter IP Address in session and save session with a name.
	- Click SSH/Auth and browse private key generated by puttygen
	- Double click on the name of saved session, you will get your server window, type password of your instance.

	Let’s begin with some basic assumptions: we have a model class called User and we want the User to know three things:

	a list of users directly linked to (me → someone)
	a list of users directly linked from (someone → me)
	a list of users directly linked, no matter to or from (e.g. if A → B and B → C, then A and C should be on B‘s linked list)
	As we can see, the relationship between two users is directed: one user initiated it and the other responded. But when looking for a path between two ‘distant’ users, we don’t care who initiated an individual relationship that could be part of the path, so we also need an undirected view on relationships.

	I left out the conﬁrmation feature, as this is easy and not particularly interesting to implement.

	Database

	Usage Note:
	-----------

	// Just put this file in assets/javascripts and require it in application.js
	// call function ajaxForm() on id of form containing file while submitting.

	Do not use both ajaxSubmit and ajaxForm on the same form. These
	functions are mutually exclusive. Use ajaxSubmit if you want
	to bind your own submit handler to the form. For example,

	test "set key value" do
	assert ConfigSetting.all.size > 1
	end

	test "found the value" do
	assert_not_nil ConfigSetting.get('email')
	end

	test "return string value" do
	email = ConfigSetting.get('email')