rubymn / ruby.mn-website Goto Github PK

View Code? Open in Web Editor NEW

10.0 8.0 2.0 62.33 MB

Source for http://ruby.mn

Home Page: http://ruby.mn

Ruby 50.17% JavaScript 7.99% CoffeeScript 0.44% CSS 24.81% HTML 14.12% Shell 2.47%

ruby.mn-website's Introduction

Ruby.MN website

This repo is no longer maintained, or deployed. It exists mainly for historical purposes.

There are known security vulnerabilities, and as such, should not be deployed to a live server.

Setup

VAGRANT BOX:

For a Vagrant box customized to this project, go to https://github.com/jhsu802701/vagrant-debian-jessie-rvm-rubymn . Because Ruby 2.1.6 and Rails 3.2 are pre-installed, the process of setting up this project after you install or reinstall this box is much quicker.

DEVELOPMENT SETUP:

Just enter the following commands:

git clone https://github.com/rubymn/ruby.mn-website.git
cd ruby.mn-website
Enter the command "sh test_app.sh".

DATABASE SEEDING

Running "rake db:seed" provides an admin user (username of "admin1" and password of "railsrocks") and a VERIFIED user (username of "007" and password of "railsrocks").

NOTES

recaptcha removed from user validation. Optionally add this back in if invalid/spam user signups really are a problem.
WARNING: ignoring activemailer delivery errors in production. This is because the new site is in a test mode. If merged back into the main site, will probably want to flip this back. This setting is in config/environments/production.rb.
If running rake gives you the error message "ERROR: encoding UTF8 does not match locale en_US Detail: The chosen LC_CTYPE setting requires encoding LATIN1.", then you need to execute the following commands to correct this: sudo -u postgres pg_dumpall > /tmp/postgres.sql sudo pg_dropcluster --stop 9.1 main sudo pg_createcluster --locale en_US.UTF-8 --start 9.1 main sudo -u postgres psql -f /tmp/postgres.sql

ruby.mn-website's People

Contributors

Stargazers

Watchers

Forkers

philcrissman jhsu802701

ruby.mn-website's Issues

Upgrade Rails to 3.2.22.5 and Ruby to 2.2.6 and then 2.3.3

Admin cannot see or approve new events submitted by users

test_admin_approve in test/functional/admin_controller_test.rb fails

I was able to log in as a verified user and submit an event. When I logged in as the admin, I was unable to see or approve the event I submitted as the verified user.

When submitting an Event don't email the group until the event is approved

users_index_test: should be UsersViewTest instead of AdminsViewTest

Minor css issues

These are for anyone to grab or for myself to fix up when I get a minute.

Line height on announcement copy should be reduced. too much spacing.
Members page URLs link styles. Perhaps hidden if no URL is provided. Could use a bit more contrast between items, maybe just a CSS3 gradient would be fine (same for home page announcements).
google map location could probably just always be displayed and not hidden with Javascript.
"for hire" page URLs are not linked
check the site in IE and make sure it is not too hideous. Have not opened it up in IE at all. While probably zero members use it, might be nice for other visitors looking to hire rubyists for example.

Do the gems in vendor/cache belong in the repository?

I'm thinking of .gitignoring them, because they make the repository bigger, and upgrading outdated gems will expand the repository even further.

test_admin_approve fails

Although the admin user can approve events, the test for this fails and needs to be revised.

In test/functional/admin_controller_test.rb, the test_admin_approve portion fails at the line "get :approve, :id => e.id, :user_id => e.user.id". The error message is:
ActionController::RoutingError: No route matches {:id=>"2", :user_id=>"13", :controller=>"admin", :action=>"approve"}

An example of a URL for approving an event is http://localhost:3000/admin/events/958/approve . The "958" is the ID number of the event. The suspect get command in the test includes the ID number of the user who submitted the event but does not specify "events".