You invited comments on the Rails class, so here are a couple of mine.
1. Sys Admin/CM Issues: I tried to install the software required for the class, but it turns out I didn't configure things properly. I was unfamiliar with getting MySQL running, and never did get Ruby 1.9.2 to be my default. I thought this might be just my problem, but i noticed one or two others having similar issues.
Maybe you or someone else can offer a Ruby on Rails sys admin course that can be a prerequisite to the Rails class. I'd love to know better how to control my development environment.
2. Databases: If I were to use a non-relational DB, like MongoDB, how might our code look different?
Thanks.
--Preston
> 1. Sys Admin/CM Issues: I tried to install the software required for the class, but it turns out I didn't configure things properly. I was unfamiliar with getting MySQL running, and never did get Ruby 1.9.2 to be my default. I thought this might be just my problem, but i noticed one or two others having similar issues.
Migrating from Ruby 1.8.7 and Rails 2 on Leopard to 1.9.3 and R3 on Snow Leopard turned out to be one of the hardest things I ever did. I worked on setting up my dev environment for a month, bookmarking dozens of web pages related to the same difficulties encountered by other people. (After four weeks, it turned out that there was one switch unflipped in RVM — everything has run well since, but I work in fear that it'll all come crashing down again at any moment.)
The class left me behind, but I am catching up on my own, and Scott's instruction is making sense in retrospect.
> Maybe you or someone else can offer a Ruby on Rails sys admin course that can be a prerequisite to the Rails class.
Would a course really help? I suspect as long as the dependencies between one package and another and another are so fragile, environment setup is always going to be a highly individual and frustrating activity.