11–20 of 54 posts
Why do you need a Linux VDI? Test locally with the Rails server, then deploy to Heroku.
A linux desktop is entirely unnecessary. But so is Heroku.
This "just deploy to Heroku" mentality is really starting to get on my nerves.
Heroku is a great product that solves real problems for a certain class of project (and user). It is not, in any way, shape or form, the solution to every problem. Stop telling people it is.
Thanks for the offer benigeri! I'll hit you up later...
thinkful.com sounds like a great resource.
shail: There were way too many problems to list here. Basically, the pattern I was falling into was as follows: I'd start a new project, start setting everything up, run into problems, fix them, run into more problems, fix them, etc... I'd have problems with everything from running bundle successfully, to deploying successfully. Then I'd get to the point where nothing would work and I'd eventually start over. Very frustrating.
The suggestions here are giving me hope and renewed enthusiasm. I'll check back later...
I'd recommend going through his tutorial rather briefly first. Like a skim. Then read through http://guides.rubyonrails.org/. Then go through is tutorial one more time. Then try building your website, while using Railscasts and StackOverflow for help.
See http://fast-reaches-9399.herokuapp.com/how-to-learn-to-progr... for more information. Good luck!
Good luck :)
My tip: DON'T USE RVM. (rbenv is a good alternative) RVM is the nº1 source of problem in Ruby envs.
The cause of problems for beginners is quite simply "change". Rails has been through a few major revisions now, and the jump from 2 to 3 dropped a lot of people (even though 3.1.x+ has been fine), and I doubt many will drop again from 3 to 4, even though there are some big changes. The problem is that with all of the changes comes a bunch of now inaccurate information that no one will update that is found easily, some with high point rankings in S.O.
The more important problem to fix though is leadership. DHH has done a great job, but either he or someone else needs to be more vocal as a single voice leading Rails. It is led by committee currently, and it shows in the lack of vision. However, despite its problems, I'm in it for the long haul. I like it a lot better than everything else.
2. Here's a volunteer hotline to call for help: http://rails.pockethotline.com/
Why do you need a Linux VDI? Test locally with the Rails server, then deploy to Heroku.
So.. You're half right IMHO! A linux desktop is entirely unnecessary. But so is Heroku. This "just deploy to Heroku" mentality is really starting to get on my nerves. Heroku is a great product that solves real problems for a certain class of project (and user). It is not, in any way, shape or form, the solution to every problem. Stop telling people it is.
if you need to get a rails app hosted NOW, it's as simple as
heroku create appname
git push heroku masterWhy do you need a Linux VDI? Test locally with the Rails server, then deploy to Heroku.
So.. You're half right IMHO! A linux desktop is entirely unnecessary. But so is Heroku. This "just deploy to Heroku" mentality is really starting to get on my nerves. Heroku is a great product that solves real problems for a certain class of project (and user). It is not, in any way, shape or form, the solution to every problem. Stop telling people it is.
My tip: DON'T USE RVM. (rbenv is a good alternative) RVM is the nº1 source of problem in Ruby envs.