Team 254 Open-Source Release: Cheesy Parts

[Jared]

Originally Posted by Jared

I'm having a hard time installing this. I've done it in the past on ubuntu, and everything worked the first time perfectly, but now I'm installing it on new machine, which doesn't have all the dependencies I usually work with.

When I run "bundle exec rake db:migrate", it fails, with the error "cannot load such file -- db". I've tried with ruby 1.9.1 and 1.9.3, and the same error happens. What am I missing?

Things are messed up with relative paths in the requires for some reason.
I solved it by removing line 16 in the Rakefile (require "db"), and replacing

Sequel::Migrator.run(DB, "db/migrations")

with

 Sequel::Migrator.run(Sequel.mysql2({ :host => "**host**", :user => "**mysql user**", :password => "**mysql  password**", :database => "**mysql database**" }), "db/migrations")

Replace the things surrounded by *'s with the actual values.

There was also an issue with require in the add starting user file. I needed to add a ./ before the path name.

Finally, the version of sequel (the ruby gem) that installed automatically was totally the wrong version and needed to be updated.

[DampRobot]

Here's the process I used to get it working on my Windows 7 laptop.

First, download and install the programs listed on the CP README. I installed Ruby 1.9.3 using Ruby windows installer (or something like that). You're going to need an Oracle account to install MySQL, just do it even though creating new accounts is a hassle. I used default installation settings for both, and installed Ruby in C:\\Ruby193.

After installing Ruby, open up a Ruby command line. You're going to be doing a fair amount of work in this window. I believe now you have to type in "gem install bundler" to install bundler.

Then download the .zip of CP. I unzipped it and put it under C:\\Users\Damp. Then, open the folder "config" in the CP main folder, and double click on the eviornment.rb file to edit it. I just edited it in Wordpad, you'll have to tell Windows which program to edit in. Then, chose a port between 8000 and 10000 and enter it in the quotation marks for port (I used 8010). I put the DB_HOST as "localhost", and put in root and 1234 for the user and password I had set up earlier when installing MySQL. I don't think URL, Gmail and Gmail pass are neccesary, I just put down my Gmail anyway. I deleted anything in the WORDPRESS_AUTH_URL, to leave only two quotation marks, like this "". Save the file and continue.

I had to add a gem later to the gemfile, but I think you can do it now. This is to supplement a gem that only works on Linux and OSX with one that works on Windows. Open the gemfile in CP main (not the .LOCK one), and add this line:

gem 'spork', '~> 0.9.0'

Then, save the file and continue.

Next, you're going to have to change the directory you're working in, to the CP main folder. Do this using the cd command. I entered cd C:\\Users\Damp\cheesy-parts-main in the Ruby command line and hit enter. Then, per the README, I entered bundle install and hit enter. This should download the various gems that CP depends on. Next, type in bundle exec rake db:migrate, which at first brought up some rake errors. I believe I eventually solved them by forcing bundler to install diferent versions of the rake gem by editing the gemfile. Make sure that you don't have multiple instances of rake in the gemfile, this will mess things up. The version of the gemfile that finally worked didn't have any other rake gems besides the rake which was there in the first place, but the fix working might have depended on the rakes that I forcibly installed earlier. Go figure.

Then, run ruby parts_server_control.rb run. If everything went as planned, you should see some message about pressing CTL-C to stop the server if everything went as it should have.

At this point, go to your trusty web browser, and enter http://localhost:[port]. I entered http://localhost:8010. Hit enter, and the CP login page should pop up. At this point, you can login with the user and pass on the CP README, and create other users.

At this point, when I try to create a new part, I get MySQL errors. This might be me, or it might be the CP software. Pat says he's working on it.

This thing required about 8 hours of debugging for me, someone who has zero experience with ruby and MySQL. If I got an error, I'd google the important part of the message, and see what others had done. Sometimes, these fixes would work and sometimes they wouldn't. Again, I couldn't have done this without Pat's gracious help.

[Zach O]

Just got it running. Thanks Pat - this looks awesome.

Quick support question: When I try restarting/stopping/starting (after the first time) it using the parts_server_control script, I get an error

https://gist.github.com/ZachOrr/6081673

Suggestions?

[DampRobot]

Originally Posted by Zach O

Just got it running. Thanks Pat - this looks awesome.

Quick support question: When I try restarting/stopping/starting (after the first time) it using the parts_server_control script, I get an error

https://gist.github.com/ZachOrr/6081673

Suggestions?

Did you try making a new part/assembly? When I tried, it gave me a MySQL error.

[Zach O]

Originally Posted by DampRobot

Did you try making a new part/assembly? When I tried, it gave me a MySQL error.

Works fine for me. Is it a permissions problem with your MySQL database?

A quick bare-bones for setting up a MySQL server on Ubuntu https://gist.github.com/ZachOrr/6081773

(try the last command on that)

[Pat Fairbank]

Originally Posted by Zach O

Just got it running. Thanks Pat - this looks awesome.

Quick support question: When I try restarting/stopping/starting (after the first time) it using the parts_server_control script, I get an error

https://gist.github.com/ZachOrr/6081673

Suggestions?

Zach, I can't reproduce this -- maybe it's something to do with the way RVM handles gems? I just realized I'm not requiring "bundler/setup" at the top of the control script like I should be, so maybe just running it as "bundle exec ruby parts_server_control.rb" will do the trick.

[Zach O]

Originally Posted by Pat Fairbank

Zach, I can't reproduce this -- maybe it's something to do with the way RVM handles gems? I just realized I'm not requiring "bundler/setup" at the top of the control script like I should be, so maybe just running it as "bundle exec ruby parts_server_control.rb" will do the trick.

Weird - running "bundle exec ruby parts_server_control.rb restart" told me it couldn't find the gems it needed, and prompted me to "bundle install", in which it reinstalled all the gems and will restart/start/stop properly now (with or without the bundle exec in front of the ruby command).

I wonder how I got it running in the first place. Anyways. Thank Pat!

[DampRobot]

Is rubygems.org down a lot? For some reason, it looks like I can't connect to it, and I can't ping it, although the rubygems.org site works just fine.

[craigboez]

254

Thanks for posting this. Its obvious that a lot of effort went into the development of this system. I've just finally gotten around to playing around with the working demo and am very impressed. While tinkering I came up with a few questions:

• How do you integrate this with your purchasing group to procure all the raw materials and parts? It looks like some of the parts just have descriptions while some add a part number and/or manufacturer name. How does the person purchasing know what to order and where from?
• Who is in charge of setting up new parts, choosing when to group things into a subassembly, what to name something, etc?
• Who keeps this updated throughout the season? Is it one single person, a group? Is it updated hourly, daily, weekly?
• Did this system solve the issues you were attempting to address?

My team tends to run pretty lean, and often the same mentors aren't there on consecutive nights. When that happens things slow down as we try to figure out what needs to happen next. A system like this could really help us keep things more focused from night to night. I'm curious to learn more about how you used it and how well it worked.

[Pat Fairbank]

Originally Posted by craigboez

254

Thanks for posting this. Its obvious that a lot of effort went into the development of this system. I've just finally gotten around to playing around with the working demo and am very impressed. While tinkering I came up with a few questions:

• How do you integrate this with your purchasing group to procure all the raw materials and parts? It looks like some of the parts just have descriptions while some add a part number and/or manufacturer name. How does the person purchasing know what to order and where from?
• Who is in charge of setting up new parts, choosing when to group things into a subassembly, what to name something, etc?
• Who keeps this updated throughout the season? Is it one single person, a group? Is it updated hourly, daily, weekly?
• Did this system solve the issues you were attempting to address?

My team tends to run pretty lean, and often the same mentors aren't there on consecutive nights. When that happens things slow down as we try to figure out what needs to happen next. A system like this could really help us keep things more focused from night to night. I'm curious to learn more about how you used it and how well it worked.

Craig,

We didn't have purchasing integration for 2013, but we're working on it for 2014. We kept track of parts needing to be ordered in a Google spreadsheet, and someone would periodically check Cheesy Parts and make sure everything that was in "needs to be ordered" status was added to the spreadsheet. Obviously, this was a bit painful.

The designers each make the naming/grouping decisions for the parts that they are working on. The addition of the parts to the system is done sometime between when a file is created and when it is first saved to PDM. You can't really save something without knowing what to call it, and so since Cheesy Parts assigns the part numbers this pretty much enforces itself.

Everyone on the team has access to the system, so the responsibility for keeping it updated is shared. Generally, whoever worked on the part last is responsible for updating its status accordingly. This wasn't totally successful, but the worst offenders were some of the mentors...

I can't speak for the rest of the team, but in the project manager / shop supervisor role that I mostly find myself in during build season, it was a huge help when confronted with a bunch of students to find tasks for, and in keeping the stress levels down.

[AdamHeard]

For someone who has no idea what they're doing with websites, someone mind posting instructions on how to install this? As if I were five please.

[DampRobot]

Originally Posted by AdamHeard

For someone who has no idea what they're doing with websites, someone mind posting instructions on how to install this? As if I were five please.

For just installing, see one of my previous posts on this thread. I have pretty much zero programming experience, so hopefully my instructions make sense for you.

Just FYI, I've had trouble reinstalling it after Pat updated the software, and haven't gotten it working since.

[schlegels]

Originally Posted by AdamHeard

For someone who has no idea what they're doing with websites, someone mind posting instructions on how to install this? As if I were five please.

I'm in the same boat as you. I am hesitate to try and follow DampRobot's instructions unless I can get confirmation that he has been able to get it working again. Our kids would really like to get this up and running for the team but I'm not sure how to get it installed.

[jacob9706]

Looks handy!
One sugestion I have is add the ability to upload a photo for each part. This would be great if students did not know a part by name and were able to see a cad drawing or a picture from a previous season related to the part when they clicked on a part!
Simple to implement but will drasticly improve the look and feel of the "part description" page!