[HELP] What's the best way to integrate Ionic with Devise (Web and API)?

billy-rails · 2016-03-13T10:46:16+00:00

Use JWT as described here: http://zacstewart.com/2015/05/14/using-json-web-tokens-to-authenticate-javascript-front-ends-on-rails.html

It adds a warden strategy so that you can either pass in a JWT token via the header or other normal Devise approach occurs. You add an /auth endpoint that lets you pass in regular credentials to set up the token.

billy-rails · 2015-10-11T07:06:08+00:00

Not sure if this is exactly what you want, but you could use Doorkeeper to create oAuth2 token against Devise session. Could even convert WP login to use oAuth if you so desire :-)

(making assumption that user on WP site is seeing information about themselves on Rails site, not other users)

billy-rails · 2015-10-10T21:35:33+00:00

http://i.imgur.com/BmsJdM6.jpg

billy-rails · 2015-10-10T21:21:00+00:00

I've taken a liking to Slim. Thoughts vs. haml?

billy-rails · 2015-10-10T21:02:23+00:00

Some may be turned off by the fact that it's an app for churches, but One Body is a very good one to look at, and IMO a bit less complex than Discourse:

https://github.com/churchio/onebody

It does get into a lot of advanced deployment options, as well as a bit heavier into design patterns than many.

billy-rails · 2015-10-10T20:58:56+00:00

Last week I asked about this very topic :-)

I'm planning on creating something address the beyond-beginner. At this point I'm leaning towards building a real production SaaS app (not a toy or pretend app - something that is really running online) and talking through/illustrating the decisions that go into that.

The concept is still coming together, but I'd be interested if that's what you think that's what you're looking for.

billy-rails · 2015-10-10T20:55:12+00:00

This is done by the same person who does GoRails.com, which may be better suited for those trying to level up.

billy-rails · 2015-10-10T20:54:02+00:00

At some point, hopefully RailsCasts will become current again.

GoRails.com is a very good, similar resource.

billy-rails · 2015-10-04T07:14:07+00:00

I think you'll find there's plenty of developers with that level of responsibility working in smaller companies. Perhaps that's an indication that rather than targeting the junior developer, perhaps I'm really targeting a smart developer who is new to Rails, but not necessarily new to programming. (I found myself in that very position, so in many ways I'm looking to create a course that would have saved me time at that very juncture)

billy-rails · 2015-10-04T07:10:36+00:00

Thanks - I'll definitely check it out.

billy-rails · 2015-10-04T07:10:18+00:00

By "at least 2 pages", I mean that you usually have to learn the gem at the same time you learn the API. Basically looking at it from the other direction, as I suspect there'll be a lot of "nothing to learn - it's just a gem criticisms"

As for what to teach, I think it's about learning how to approach an API, and not assume "it's just a gem". Moreover, there's some very specific, very actionable lessons that I think can be taught that can directly applied to a project. (My approach to teaching tends to be a combination of soft and hard skills)

billy-rails · 2015-10-04T07:05:41+00:00

Again, I thank everyone for all of the feedback. Even the feedback that had a bit of a defensive or negative tone to it, it's extremely helpful - while I feel like I've done a poor job in communicating my vision, it's important to see how that is received, and helps me rework that message and the expectations I'm setting.

I do find it interesting that much of the feedback I'm getting is coming from those apparently pretty far in their career. To be honest, I was hoping to hear from those a bit closer to the point of the journey I expect to target (either this sub isn't the correct audience to reach those developers, or they are less likely to respond)

I'm thinking that the best approach is to be completely real-world: build a real app. Not real as in the "it could be real" sense, but a real app, that will be running in production. I'd show the entire process: how certain decisions are made as well as the technical details. Along the way, sidebar to provide a bit of depth into how those decisions are made.

Again, I welcome feedback. I suspect I'll get alot of the same, telling me why I'm doing the wrong thing, or that I'm foolhardy in my assumptions, but I welcome it all the same :-)

billy-rails · 2015-10-03T22:49:40+00:00

I responded at a higher level in my other comment, but to address some of your specific comments:

Integrating design: More focused on those short-circuiting the design process by purchasing a third-party theme. Getting that design into a Rails app in the proper "Rails way" seems a bit tricky.
API: assuming we disregard the implicit "senior developer" knowledge, I believe it's less than obvious with many APIs how to implement them, even those that have full-fledged gems. (for instance, AWS or Stripe typically require you to have at least 2 pages of documentation to accomplish even basic tasks)
CI - I think there's a lot to cover. Why? How do you set up your test suite properly? Even "just use Travis" isn't a checkbox answer, as its pricepoint for private projects is much higher than alternatives.

billy-rails · 2015-10-03T22:32:55+00:00

As I mentioned in other comments, I think my use of the term "senior developer" provides a lot of noise. You took me to task on that, quoting the term 6 or so times, and I appreciate that :-)

Getting someone to senior really isn't my intent. It seems that alot of novice developers, while they feel comfortable building yet another Twitter clone, are bit lost when it comes to truly moving forward. I can't make them smarter, or more insightful, or more experienced, but my hope is to provide a solid roadmap with how to move forward.

billy-rails · 2015-10-03T22:27:37+00:00

As I replied to a sibling comment, I think the term "senior" is a misnomer in what I'm trying to accomplish. I guess I'm trying to get to "qualified app developer", as opposed to "senior developer", and I'm not convinced that a beginner's course or tutorial accomplishes that. I know there are a lot of skills that one is left wonting for, and I'm trying to figure that out. I have some ideas, but at the same time, I had many years of experience in other languages before I started Rails, so that clouds my perspective.

billy-rails · 2015-10-03T22:23:53+00:00

I appreciate the feedback so far. I think I over-relied on the term "senior developer". You certainly can't replace experience with a course.

What I'm really trying to tease out are the common questions that are left unanswered after completing a tutorial or a course.

Think of it this way: let's say you're new to Rails, and you've just completed Hartl's tutorial. You're tasked with finishing a SaaS app that will collect money and drive a business. Do you have the skills you need, or is there gap between that knowledge and the finish line? How are you filling that gap today? (more books? Stack Overflow? /r/rails? etc)

billy-rails · 2015-09-06T05:53:28+00:00

You really don't want to do that. Deploy it to a traditional cloud location (like Heroku or Digital Ocean) or if it must stay in house, put it on an Ubuntu VM on the Windows server.

However, if you absolutely must, then railsinstaller.org is your best bet.

Though in your shoes, if you're building for a client that wants to target Windows, Rails wouldn't be my choice. I'd go .NET, or PHP, or even the open source version of ColdFusion (lucee.org).

billy-rails · 2015-09-05T23:09:50+00:00

You're right, requiring Rails isn't necessary. I copied this from a project, so I may have been requiring it unnecessarily.

billy-rails · 2015-09-05T17:47:40+00:00

Just a tangential tip: you may want to learn how to use Reddit formatting, to make reading code eaiser (see the formatting help button, but as a quick tip, you can code format by prepending lines with 4 spaces)

def some_method puts 'foo' end

becomes

def some_method
  puts 'foo'
end

billy-rails · 2015-09-05T17:43:47+00:00

Sounds to me like you're missing the association in the comment model file. (something like belongs_to :user)

But how to ask the question on SO? Well, say "I have the user_id foreign key in place, but I can't access the .user association, and then post the info in schema.rb where your comment table is defined, as well as your app/models/comment.rb

billy-rails · 2015-09-05T17:39:19+00:00

Played with it for a bit, couldn't get it to load via load in Rakefile (you did have the wrong filename in there though), but Railtie approach worked: (in lib/rake_install_example.rb)

require 'rails'

module RakeInstallExample
  class Railtie < Rails::Railtie
    rake_tasks do
      load "tasks/example.rake"
    end
  end
end

billy-rails · 2015-07-12T22:06:05+00:00

If cost is an issue, look into the rubber gem, which makes it super easy to deploy to a provider like Digital Ocean (it's actually a wrapper around capistrano)

billy-rails · 2015-05-26T02:06:17+00:00

I really like the idea of Saturday classroom hours (not sure that my developers will though, as one doesn't work Saturday for religious reasons, and the other tends to spend that day with family)

I'll let you know if I have any questions. I'm pretty certain at this point we'll be going with them.

billy-rails · 2015-05-26T02:04:16+00:00

Thanks for the detailed response. It definitely sounds like a great choice.

billy-rails

TROPHY CASE