Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-17T17:36:24Z

Asorgiu: Changes from project contact's feedback

'''CSC517 Final Project - E1744 Github Metrics'''

'''(asorgiu, george2, mdunlap, ygou14)'''

== Proposed Design Document ==

===Description===
We will add a new feature to provide Expertiza with Github metrics (for example, number of committers, number of commits, number of lines of code modified, number of lines added, number of lines deleted.) from each group’s submitted repo link. This information should prove useful for differentiating the performance of team members for grading purposes. It may also help instructors to predict which projects are likely to be accepted/rejected (even before the final due dates).

===Work to be done===
This project is divided into two parts. One is to extract Github metadata of the submitted repos and pull requests. The second part is to build a classifier (e.g., Bayesian) to do the early prediction on some projects that are likely to fail. This prediction is based on more than 200 past projects (Fall 2012- Fall 2016). Based on the meta-data from students repos/pull requests, we can warn both authors and teaching staff if our model predicts that some projects are likely to fail.

The methodology of this project is to add a means to monitor the individual contributions of various team members throughout the duration of project in order to quantitatively access their work. This will aid the teaching staff and team members during the review process as well as improve visibility to a student of the work he or she has committed.

====Extract Github metadata====

=====Data Flow=====

The code should sync the data with Github by use of a task scheduler in Expertiza.

TO BE DONE: ADD USE CASE DIAGRAM

=====Architectural Design=====
This feature has similar functionality with a web crawler, which is crawling the data from a server and store locally. So that for the architectural style of our subsystem, we would like to choose client/server style, which segregates the system into two applications, where the client makes requests to the server whenever a user is looking for the metrics. In many cases, the server is a database with application logic represented as stored procedures, in our case, is Github.

=====UML=====
[[File:1744 design.png|frame|center|30px|30px]]

=====Database Schema Changes=====
[[File:1744_db_schema.png|frame|center|30px|30px]]

A new table called '''github_contributors''' is created to store the data for each committer. The table contain's the committer's email, github_id and all the metrics associated with a project. At the moment we handle the following metrics:
* Committer email - commiter_url
* Committer id - commiter_id
* Total number of commits - total_commits
* Number of files changed - files_changed
* Lines of code changed - lines_changed
* Lines of code added - lines_added
* Lines of code removed - lines_removed
* Lines of code added that survived until final submission - lines_persisted.

An index on committer_id is added to enable search.

A new table called '''submission_records_github_contributors''' which acts as a reference between the '''submission_records''' and '''github_contributors''' tables. It has two columns:
* github_contributor_id - Foreign Key to '''github_contributors''' table.
* submission_record_id - Foreign Key to '''submission_records''' table.

A composite unique key constraint is added on ''github_contributor_id'' and ''submission_record_id''.

====Test Plan====

The tests will use rspec to validate the response to the metrics from github and displaying the various metrics. These tests will be test the data in new tables '''submission_records_github_contributors''' and '''github_contributors''' as well as expand the existing tests on '''submission_records'''.

# Test 1:
## Login as instructor6
## Go to submission page
## Validate that metrics are pulled in from github
# Test 2:
## Login as student
## Go to submission page
## Confirm the student's metrics values

=====Unit Tests=====

{| class="wikitable"
! colspan="3" | Unit Test Summary
|-
! Method
! Parameter
! Expected result
|-
| get_metrics
| team_id = null
| Null / Exception
|-
| get_metrics
| team_id = Invalid team_id
| Null / Exception
|-
| get_metrics
| team_id = valid_team_id
| List of metrics for all the committers in the team.
|-
|}

====Build a classifier====
THIS WILL NOT BE IMPLEMENTED AS PART OF THIS PROJECT. This is future work to be done.

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-08T02:16:09Z

Asorgiu: /* Data Flow */

'''CSC517 Final Project - E1744 Github Metrics'''

'''(asorgiu, george2, mdunlap, ygou14)'''

== Proposed Design Document ==

===Description===
We will add a new feature to provide Expertiza with Github metrics (for example, number of committers, number of commits, number of lines of code modified, number of lines added, number of lines deleted.) from each group’s submitted repo link. This information should prove useful for differentiating the performance of team members for grading purposes. It may also help instructors to predict which projects are likely to be merged.

===Work to be done===
This project is divided into two parts. One is to extract Github metadata of the submitted repos and pull requests. The second part is to build a classifier (e.g., Bayesian) to do the early prediction on some projects that are likely to fail. This prediction is based on more than 200 past projects. The features above should be used, together with some temporal features (e.g. the temporal pattern of this team’s commits so far). Eventually, we would like to e-mail students whose metrics are bad, giving them advice on how to improve.

The purpose of this project is to add a means to monitor the individual contributions of various team members throughout the duration of project in order to quantitatively access their work. This will aid the teaching staff and team members during the review process as well as improve visibility to a student of the work he or she has committed.

====Extract Github metadata====

=====Use Cases=====

=====Data Flow=====

The code should sync the data with Github whenever someone (student or instructor) looks at a view that shows Github data.

=====Architectural Design=====

=====UML=====

=====Database Schema Changes=====
[[File:db_github_schema.png|frame|center]]

A new table called '''github_contributors''' is created to store the data for each committer. The table contain's the committer's email, github_id and all the metrics associated with a project. At the moment we handle the following metrics:
* Committer email - commiter_url
* Committer id - commiter_id
* Total number of commits - total_commits
* Number of files changed - files_changed
* Lines of code changed - lines_changed
* Lines of code added - lines_added
* Lines of code removed - lines_removed
* Lines of code added that survived until final submission - lines_persisted.

An index on committer_id is added to enable search.

A new table called '''submission_records_github_contributors''' which acts as a reference between the '''submission_records''' and '''github_contributors''' tables. It has two columns:
* github_contributor_id - Foreign Key to '''github_contributors''' table.
* submission_record_id - Foreign Key to '''submission_records''' table.

A composite unique key constraint is added on ''github_contributor_id'' and ''submission_record_id''.

=====Test Plan=====

The tests will use stubs to simulate the number of commits from github and displaying the various metrics. These tests will be test the data in new tables '''submission_records_github_contributors''' and '''github_contributors''' as well as expand the existing tests on '''submission_records'''.

====Build a classifier====
THIS WILL NOT BE IMPLEMENTED AS PART OF THIS PROJECT. This is future work to be done.

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-07T19:23:23Z

Asorgiu:

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-07T19:18:07Z

Asorgiu: /* Database Schema Changes */

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-07T19:17:38Z

Asorgiu:

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-07T19:15:21Z

Asorgiu:

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-07T19:13:28Z

Asorgiu: /* Build a classifier */

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-05T17:30:53Z

Asorgiu: Add section headers

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-05T17:25:47Z

Asorgiu:

'''CSC517 Final Project - E1744 Github Metrics'''

'''(asorgiu, george2, mdunlap, ygou14)'''

== Proposed Design Document ==

===Description===

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-05T17:22:15Z

Asorgiu:

CSC517 Final Project - E1744 Github Metrics

(asorgiu, george2, mdunlap, ygou14)

CSC/ECE 517 Spring 2017/finalproject E1744

2017-04-04T23:13:23Z

Asorgiu: Created page with "CSC517 Final Project - E1744 Github Metrics (asorgiu, bzamani, george2, mdunlap)"

CSC517 Final Project - E1744 Github Metrics

(asorgiu, bzamani, george2, mdunlap)

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T21:30:36Z

Asorgiu: /* Testing Instructions */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

===Testing Instructions===
====First task====
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T21:29:31Z

Asorgiu: /* Testing using Selenium IDE */

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T21:29:10Z

Asorgiu: /* Running the Project Locally */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Remotely==
We have hosted our forked repo so you can review our changes here:

http://138.197.104.185:3000/

Suggested login for Instructor privileges is 'instructor6' with password 'password'. To login as a student, you can use 'student5000' with password 'password'

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T21:25:01Z

Asorgiu: /* Tasks Identified */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, make sure you are managing assignments, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==
Those who contributed to the project could run the project locally by going to a terminal window, navigating to the project folder and running the single command:

rails server

If the project was to be run again after changes to project code have been made, the commands to run from the terminal window would be as follows:

bundle install
rails s

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T21:24:21Z

Asorgiu: /* Tasks Identified */

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information). The javascript from the file _due_dates.html.erb was also moved to the new signup.js file.
This functionality can be tested by logging in as an instructor, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==
Those who contributed to the project could run the project locally by going to a terminal window, navigating to the project folder and running the single command:

rails server

If the project was to be run again after changes to project code have been made, the commands to run from the terminal window would be as follows:

bundle install
rails s

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

CSC/ECE 517 Spring 2017/oss E1727

2017-03-22T20:48:20Z

Asorgiu: Update task info

==Introduction==
This project was completed as part of a greater open source project called Expertiza.

Expertiza is a web application platform, similar to wikipedia, which offers teachers and students a way to organize for group assignments and porjects. By using Expertiza, students have the ability to submit and coordinate peer-review learning objects (articles, code, web sites, etc). The Expertiza project is supported by the National Science Foundation.

Expertiza offers several features which are useful to a classroom-style learning environment. Among those several features, this project represents a contribution to the organization of the code used for assignment signup sheets.

===Background===
The work for this project was completed by a group of three students from NC State. However, the project was completed according to guidelines provided by a coordinator who works with Expertiza.

Following the guidelines provided, the group worked to clean up a portion of the Expertiza project code through refactorization and reorganization. More specifically, logical code needed to be separated from portions of the project which were not responsible for containing code for the functionality of the application.

===Motivation===
The motivation for this project was to make the project code easier for programmers to read by compartmentalizing portions of the code to separate locations in the project according to the functionality of the code.

The scope of this project was limited to functionalities associated with the signup sheet. This meant that logical code that was embedded in "view" (a folder containing html formatting and design code) should be moved to a more appropriate location, the "helpers" folder (this folder contains compartmentalized auxiliary functions that "help" with other parts of the project).

===Tasks Identified===
'''Documents:''' _add_signup_topics.html.erb, _due_dates.html.erb
* Move javascript code to assets (folder): There was some javascript at the bottom of the file _add_signup_topics.html.erb. This was moved to a new file app/assets/javascripts/signup.js. The functions were modified to pass in the number of teams that needed to be toggled (since it is now in a separate file without access to that information)
This functionality can be tested by logging in as an instructor, then click the "Edit" button of an assignment (the little pencil icon on the right), then choose the "Topic" tab. If you click "Hide all teams" link, all team names and team member unity ids will be hidden. Click the link again and the content will be shown. If you click individual top names, it should hide/show only one team's info.

'''Documents:''' _suggested_topic.html.erb, intelligent_topic_selection.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Documents:''' _all_actions.html.erb, _topic_names.html.erb
* Move logical code to helper file and assign self-explanatory method names.

'''Testing:'''
* Create a test file named sign_up_sheet_helper_spec.rb in spec/helpers
* Write test cases for all methods in sign_up_sheet_helper.rb using factories

====Classes====
* sign_up_sheet_helper.rb
* sign_up_sheet_helper_spec.rb

===Project Modifications===

==== New Method: check_topic_due_date_value() ====
<nowiki> def check_topic_due_date_value(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
due_date = get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id, review_round)
DateTime.parse(due_date.to_s).strftime("%Y-%m-%d %H:%M").in_time_zone
end</nowiki>

==== New Method: get_topic_deadline() ====
<nowiki> def get_topic_deadline(assignment_due_dates, topic_id, deadline_type_id = 1, review_round = 1)
topic_due_date = TopicDueDate.where(parent_id: topic_id,
deadline_type_id: deadline_type_id,
round: review_round).first rescue nil
if !topic_due_date.nil?
topic_due_date.due_at
else
assignment_due_dates[review_round - 1].due_at.to_s
end
end</nowiki>

==== New Method: get_suggested_topics() ====
<nowiki> def get_suggested_topics(assignment_id)
team_id = TeamsUser.team_id(assignment_id, session[:user].id)
teams_users = TeamsUser.where(team_id: team_id)
teams_users_array = Array.new
teams_users.each do |teams_user|
teams_users_array << teams_user.user_id
end
@suggested_topics = SignUpTopic.where(assignment_id: assignment_id, private_to: teams_users_array)
end</nowiki>

==== New Method: get_intelligent_topic_row() ====
<nowiki> def get_intelligent_topic_row(topic, selected_topics)
row_html = ''
if !selected_topics.nil? && selected_topics.size != 0
for selected_topic in @selected_topics
if selected_topic.topic_id == topic.id and !selected_topic.is_waitlisted
row_html = '<tr bgcolor="yellow">'
elsif selected_topic.topic_id == topic.id and selected_topic.is_waitlisted
row_html = '<tr bgcolor="lightgray">'
else
row_html = '<tr id="topic_"' + topic.id.to_s + '>'
end
end
else
row_html = '<tr id="topic_"' + topic.id.to_s + ' style="background-color:' + get_topic_bg_color(topic) + '">'
end
row_html.html_safe
end</nowiki>

==== New Method: get_topic_bg_color() ====
<nowiki> def get_topic_bg_color(topic)
'rgb(' + (400*(1-(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).count,1].min-1)+1)/2))
.to_i.to_s + ',' + (400*(Math.tanh(2*[@max_team_size.to_f/Bid.where(topic_id:topic.id).
count,1].min-1)+1)/2).to_i.to_s + ',0)'
end</nowiki>

==== New Method: render_participant_info() ====
<nowiki> def render_participant_info(topic, assignment, participants)
name_html = ''
if !participants.nil? && participants.size > 0
chooser_present = false
for participant in @participants
if topic.id == participant.topic_id
chooser_present = true
if assignment.max_team_size > 1
name_html += ' ' + participant.team_name_placeholder + ' '
end
name_html += 'participant.user_name_placeholder'
if participant.is_waitlisted
name_html += '(waitlisted)'
end
name_html += ' '
end
end
unless chooser_present
name_html += 'No choosers.'
end
end
name_html.html_safe
end</nowiki>

===Changes to the View===

==== Impact Analysis ====
*

===Affected Classes===
*

==Running the Project Locally==
Those who contributed to the project could run the project locally by going to a terminal window, navigating to the project folder and running the single command:

rails server

If the project was to be run again after changes to project code have been made, the commands to run from the terminal window would be as follows:

bundle install
rails s

==Testing using Selenium IDE==

===Testing Instructions===

==Future Work==

Development:Setup:OSX

2017-03-14T01:03:47Z

Asorgiu: add login info

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>

==Set up secrets file==
<pre style="white-space:normal;">cp config/secrets.yml.example config/secrets.yml</pre>

==Setup Bower==
First, install bower with npm (install npm first if not already installed)
<pre style="white-space:normal;">npm install bower -g</pre>
Then run this from the expertiza directory
<pre style="white-space:normal;">bower install --allow-root</pre>

==Start rails server==
<pre style="white-space:normal;">rails server</pre>
Then direct your browser to <code>http://localhost:3000</code>

You can log in using instructor6. student5000, student5001, etc. are good too.
The password for any account is "password".

====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-14T01:01:06Z

Asorgiu: Bower setup

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>

==Set up secrets file==
<pre style="white-space:normal;">cp config/secrets.yml.example config/secrets.yml</pre>

==Setup Bower==
First, install bower with npm (install npm first if not already installed)
<pre style="white-space:normal;">npm install bower -g</pre>
Then run this from the expertiza directory
<pre style="white-space:normal;">bower install --allow-root</pre>

==Start rails server==
<pre style="white-space:normal;">rails server</pre>
Then direct your browser to <code>http://localhost:3000</code>

====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-14T00:48:49Z

Asorgiu:

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>

==Set up secrets file==
<pre style="white-space:normal;">cp config/secrets.yml.example config/secrets.yml</pre>

====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T17:01:58Z

Asorgiu:

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:59:38Z

Asorgiu: /* DEPRECATED [Use .sql script above instead] */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

====DEPRECATED [Use .sql script above instead of the next 4 steps]====
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

====/DEPRECATED====

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:58:55Z

Asorgiu: /* Set the MySql Root Password */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>

====Run SQL script to scrub DB====
Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uEMDJhNjZVOUFTWmM/view?usp=sharing)
Download the file, unzip it and dump to MySQL.
<pre style="white-space:normal;">mysql -uroot -p -h localhost < expertiza-fall2016-scrubbedDB.sql</pre>

====DEPRECATED [Use .sql script above instead]====
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

====/DEPRECATED====

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:57:28Z

Asorgiu: /* DEPRECATED [Use .sql script instead] */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====DEPRECATED [Use .sql script above instead]====
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

====/DEPRECATED====

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:56:32Z

Asorgiu: /* DEPRECATED */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====DEPRECATED [Use .sql script instead]====
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>
====/DEPRECATED====

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:55:53Z

Asorgiu:

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====DEPRECATED [Use .sql script instead]====
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql

=====Create the Expertiza User=====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

=====Create the Databases=====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

=====Grant Privileges to the Expertiza User=====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>
====DEPRECATED====

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T16:54:29Z

Asorgiu: /* Log in to MySql */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====DEPRECATED [Use .sql script instead]
=====Log in to MySql=====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====DEPRECATED

====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:34:26Z

Asorgiu: /* Build the Expertiza Database */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml</pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml</pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:34:05Z

Asorgiu: /* Build the Expertiza Database */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
First, you have to copy the sample database config to a real one.
<pre style="white-space:normal;">cp config/database.yml.example config/database.yml<pre>
Then edit the file and put your mysql password in there so it can log into the db
<pre style="white-space:normal;">vi config/database.yml<pre>
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:29:29Z

Asorgiu: /* Grant Privileges to the Expertiza User */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on expertiza_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on expertiza_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:29:07Z

Asorgiu: /* Create the Databases */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database expertiza_development;</pre>
<pre style="white-space:normal;">create database expertiza_test;</pre>

====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:22:40Z

Asorgiu: /* Install Bundled Gems */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>

<pre style="white-space:normal;">bundle install</pre>

Possible alternate step if _bundle install_ command has build errors:
<pre>
$ bundle config build.eventmachine --with-cppflags=-I/usr/local/opt/openssl/include
$ brew install apple-gcc42
$ brew unlink apple-gcc42
$ brew link apple-gcc42
$ export CC=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/gcc-4.2
$ export CXX=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/g++-4.2
$ export CPP=/usr/local/Cellar/apple-gcc42/4.2.1-5666.3/bin/cpp-4.2
</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database pg_development;</pre>
<pre style="white-space:normal;">create database pg_test;</pre>
====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:17:10Z

Asorgiu: /* Install Bundled Gems */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem (set it to a valid location, your path may vary):
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>
<pre style="white-space:normal;">bundle install</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database pg_development;</pre>
<pre style="white-space:normal;">create database pg_test;</pre>
====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:16:22Z

Asorgiu: /* Install Bundled Gems */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem:
<pre style="white-space:normal;">export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/</pre>
<pre style="white-space:normal;">bundle install</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database pg_development;</pre>
<pre style="white-space:normal;">create database pg_test;</pre>
====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:15:04Z

Asorgiu: /* Install Native Expertiza Dependencies */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz openssl</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem:
<pre style="white-space:normal;">export JAVA_HOME=/etc/alternatives/java_sdk</pre>
<pre style="white-space:normal;">bundle install</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database pg_development;</pre>
<pre style="white-space:normal;">create database pg_test;</pre>
====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>

Development:Setup:OSX

2017-03-12T15:14:39Z

Asorgiu: /* Install Ruby v. 1.8.7 */

==Prerequisites==
* You must have shell access
* You must have root access (via sudo), or the required software must already be installed
==Install Git==
[http://git-scm.com/download/mac Git for OS X]

==Get Expertiza==
====Fork Expertiza to your Github====
* If you don't have a Github account, register one, and remember the password!!
* go to https://github.com/expertiza/expertiza and click on the "Fork" button on the upper right side.
* When asked "Where should we fork this repository?" choose your account, which usually looks like this "@YourUsername"
* Then go to https://github.com/[YourUsername]/expertiza and click on the "Clone or Download" button
* Copy the url, which usually looks like "https://github.com/[YourUsername]/expertiza.git"
* Then go to your terminal and go to a folder of your choice where the codes will be downloaded into.
* To clone the project, type in "git clone https://github.com/[YourUsername]/expertiza.git"
* when asked for a password, enter your password

====Merge your changes to Expertiza====
* When you're done editing the code, commit the code to your local repository by executing this in terminal:
** git add -A #mark all changed files to be committed to the repository
** git commit -m "say what you have done to the code" #commit your changes to the local repository
** git push #sync your changes to the remote repository
* Do commit as often as needed to store the states of the code. Do commit before you do changes that you're not sure about. It'd allow you to revert back to your previous states if you screw up the code.
* Do push less often (maybe every 5-10 commits)
* Before requesting for a merge, please refactor your code and put comments. Bad code won't be merged!
* After you're done with beautifying your project, go to https://github.com/[YourUsername]/expertiza, and click on "New pull request" on the left side.
* Your code will be reviewed and merged if the quality is good enough!

====[DEPRECATED. DO NOT USE UNLESS ADVISED]====
=====Expertiza Repository URLs=====
* (ssh, read/write) git@github.com:expertiza/expertiza.git
* (https, read/write) https://github.com/expertiza/expertiza.git
* (git, read-only) git://github.com/expertiza/expertiza.git
=====Default [DEPRECATED]=====
<pre style="white-space:normal;">git clone <remote></pre>
<pre style="white-space:normal;">git clone git@github.com:expertiza/expertiza.git</pre>
=====Options =====
<pre style="white-space:normal;">git clone -b <branch> <remote></pre>
<pre style="white-space:normal;">git clone -b production git@github.com:expertiza/expertiza.git</pre>

==Install Homebrew==
http://mxcl.github.io/homebrew

==Install RBENV==
<pre>
$ brew update
$ brew install rbenv
$ brew install ruby-build
</pre>

==Install Ruby v. 2.1.5==
https://github.com/sstephenson/ruby-build/wiki#installing-187-on-os-x-108-mountain-lion

==Install Native Expertiza Dependencies==
Dependencies are for the gems raspell, rjb, nokogiri, and mysql.
<pre style="white-space:normal;">brew install aspell gcc47 libxml2 libxslt graphviz</pre>

==Install Bundled Gems==
Set JAVA_HOME for the rjb gem:
<pre style="white-space:normal;">export JAVA_HOME=/etc/alternatives/java_sdk</pre>
<pre style="white-space:normal;">bundle install</pre>

==Set Up the Database==
====Set the MySql Root Password====
This step is not necessary, but it is advised to set a root mysql password.
<pre style="white-space:normal;">mysqladmin -u root password</pre>
====Log in to MySql====
<pre style="white-space:normal;">mysql -uroot -p</pre>
The following commands are executed inside mysql
====Create the Expertiza User====
<pre style="white-space:normal;">create user expertiza@localhost;</pre>

====Create the Databases====
<pre style="white-space:normal;">create database pg_development;</pre>
<pre style="white-space:normal;">create database pg_test;</pre>
====Grant Privileges to the Expertiza User====
<pre style="white-space:normal;">grant all on pg_development.* to expertiza@localhost;</pre>
<pre style="white-space:normal;">grant all on pg_test.* to expertiza@localhost;</pre>

==Build the Expertiza Database==
Notice: You may need to prepend the following commands with <code>bundle exec</code>.
<pre style="white-space:normal;">rake db:migrate</pre>
<pre style="white-space:normal;">rake db:test:prepare</pre>
====Import Production Data (Optional)====
This step requires that you have your ssh private/public key pairs loaded in the production server under the rails user. 
[[How to Add SSH Keys to the Expertiza Production Server]] 
You must run the following command from your local Expertiza project directory.
<pre style="white-space:normal;">cap production load_data</pre>