Page 1 of 3 | Next »
[21:33:09] jahbrewski: flappynerd: not a fan of Heroku? The platform has greatly improved the past year or so
[21:33:59] jahbrewski: flappynerd: if my clients are paying 30-40k for an app a couple hundred bucks per month isn't breaking their banks :)
[21:35:54] jahbrewski: flappynerd: Demerzel fair enough. I like the sane defaults Heroku provies though. Feals very rails-esque
[21:37:34] jahbrewski: For a basic rails site though, you really can't beat heroku for ease of setup. And time=money
[21:38:21] jahbrewski: That's something I find developers forget. "But why would I pay for that when I could do X" ...because X takes 10x as long..
[21:41:46] jahbrewski: bronson: I've got plently of projects more complex than a scaffold demo on Heroku :)
[21:43:45] jahbrewski: bronson: Have you checked out their playbook? http://playbook.thoughtbot.com/
[21:50:14] jahbrewski: which is a good rule of thumb to live by as a developer. At a certain point Rails itself becomes more of a hindrance than a helper..
[21:56:30] jahbrewski: rubyonrails645: I don't have much experience with beanstalk.. I tried it a while back and the interface just seemed rough/bad
[22:02:00] jahbrewski: rubyonrails645: well, you have to factor in the cost of switching to a new platform. and the time.
[22:02:43] jahbrewski: rubyonrails645: Take a look at your current hosting expenses, calculate your estimated savings, minus the cost of the switch, and decide if it makes sense
[22:04:27] jahbrewski: rubyonrails645: And they make it extremely easy. Literally dragging a slider. Granted you'll want to invest some time into performance enhancements once you start scaling.
[22:05:20] jahbrewski: rubyonrails645: Don't prematurely optimize though. Don't worry about scaling until you have to. Scaling is a great problem to have.
[22:06:48] jahbrewski: rubyonrails645: Sure thing. Those are my thoughts. Certainly not applicable for everyone. I run a development shop, so time is literally money for us.
[22:09:33] jahbrewski: YourManCJ: Also depends on how you learn best. There are videos everywhere if that's your thing. Books. Blog posts. Etc.
[22:10:42] jahbrewski: YourManCJ: Working organically through your own project is probably the best way, once you get some of the fundamentals down.
[22:11:24] jahbrewski: YourManCJ: I posted an ad on Craitslist that I was a rails dev (hadn't built an app in my life), took on a client project, and learned on the job
[22:13:31] jahbrewski: rubyonrails645: I've got a few mobile apps that upload to my server first and then s3
[22:16:01] jahbrewski: YourManCJ: Yeah, ENV vars work well. I've used Figaro before for managing config vars: https://github.com/laserlemon/figaro
[22:19:03] jahbrewski: YourManCJ: Truly understanding git is a valuable investment in yourself as a developer
[22:19:59] jahbrewski: jahbrewski: My server essentially acted as a proxy. It handled the upload to s3.
[22:24:06] jahbrewski: bpr_admin: I find it hard to believe the app has no database.. no real reason to use Rails if that's the case
[22:26:36] jahbrewski: bpr_admin: If so, open one up and see if you see something like "<ActiveRecord::Base" at the top
[22:27:30] jahbrewski: bpr_admin: That's fine. But you've got your answser. You need to find out what happened to your config/database.yml file
[22:35:36] jahbrewski: Looks like you can either use a config/database.yml file to configure your database, or connect to the database via an environment variable (ENV['DATABASE_URL'])
[22:36:37] jahbrewski: bpr_admin: http://edgeguides.rubyonrails.org/configuring.html#configuring-a-database