Hi! I''m new to Ruby and Rails and I''ve got previous experience with PHP, some C/Objective C and Java. I''ve just finished the short "first app" tutorial on rubyonrails.org. RoR seems great and I really like it after this brief intro :) A question. What should an app contain? I mean, is it the whole site or should I split the site up in several apps? Most tutorials only have some basic intro that creates like a ''blog''. Yeah, that fits good inside a single app. But what about if you have one part of your site that''s a blog, another part is a forum, another is a community thing, another is a task manager...and so on. Do you see what I mean? Should I split all these into several ''apps''? Perhaps it''s a stupid question, but as I said, I AM new to this so... :) Cheers! Linus -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Mar 15, 2011, at 5:20 PM, Linus Pettersson wrote:> Hi! > > I''m new to Ruby and Rails and I''ve got previous experience with PHP, > some C/Objective C and Java. I''ve just finished the short "first app" > tutorial on rubyonrails.org. RoR seems great and I really like it > after this brief intro :) > > A question. What should an app contain? I mean, is it the whole site > or should I split the site up in several apps? Most tutorials only > have some basic intro that creates like a ''blog''. Yeah, that fits good > inside a single app. But what about if you have one part of your site > that''s a blog, another part is a forum, another is a community thing, > another is a task manager...and so on. > > Do you see what I mean? Should I split all these into several ''apps''? > > Perhaps it''s a stupid question, but as I said, I AM new to this > so... :)Welcome to the party, I just got here myself... I would say to answer your question that it matters more what your various apps have in common or need to share. Let''s say you have a blog comment model and a forum post model, and they both need a user to sign in in order to be able to say who created each -- that would argue for maybe putting each of these "apps" together in the same application where they could share the common sign-in and other resources. On the other hand, if you don''t need to share anything, there''s a lot good to be said for having the bare-est minimum in your application. Less to break, for one thing. You could also expose your login as a service from one "user management" app, and consume it from two others. Luckily, these sorts of choices are something you can revise later on, as a Rails app can seem a bit like a box of Legos, where you can snap things together and good tests let you refactor at whim. Walter> > Cheers! > Linus > > -- > You received this message because you are subscribed to the Google > Groups "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails- > talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > . > For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en > . >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
These parts of the site (forum, community thing, task manager) you''ll would basically do with Rails Scaffolds, creating each resource of your application and each important thing of the app (comments, posts, members) you''d define in models. You would design your views, use some gem for authentication.. basically it. I think that´s it, basically. I tip I can give you is start making something real, coding for sure :D .. in your free time, address some project you have in mind and with no pressure or compromise, start developing it! Oh, and don''t forget http://railscasts.com I''ve already learned a lot of things with its screencasts! Cheers! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hi! Thank you for your answers :) I really appreciate it. I have checked out some Railscasts and they are great. They may be a little too specific for me at the moment though. Are there any good Rails-tutorials out there for a complete website? A website that has more functions than just a ''blog'' with comments. Or maybe just a complete site on github or something where I can browse some code to get the hang of the structure of a complete site? :) Best Regards Linus On 16 mar, 02:56, Rodrigo Alves Vieira <rodrig...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> These parts of the site (forum, community thing, task manager) you''ll would > basically do with Rails Scaffolds, creating each resource of your > application and each important thing of the app (comments, posts, members) > you''d define in models. You would design your views, use some gem for > authentication.. basically it. > > I think that´s it, basically. I tip I can give you is start making something > real, coding for sure :D .. in your free time, address some project you have > in mind and with no pressure or compromise, start developing it! > > Oh, and don''t forgethttp://railscasts.comI''ve already learned a lot of > things with its screencasts! > > Cheers!-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Mar 16, 2011 at 10:04 AM, Linus Pettersson < linus.pettersson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi! > > Thank you for your answers :) I really appreciate it. > I have checked out some Railscasts and they are great. They may be a > little too specific for me at the moment though. >Start with the Rails guides. It isn''t a whole website, but it''s all of the initial steps required to build one: http://guides.rubyonrails.org/ I also hear good things about Rails for Zombies, but haven''t had a chance to check it out: http://railsforzombies.org/ Best Wishes, Peter> > Are there any good Rails-tutorials out there for a complete website? A > website that has more functions than just a ''blog'' with comments. Or > maybe just a complete site on github or something where I can browse > some code to get the hang of the structure of a complete site? :) > > Best Regards > Linus > > > > On 16 mar, 02:56, Rodrigo Alves Vieira <rodrig...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > These parts of the site (forum, community thing, task manager) you''ll > would > > basically do with Rails Scaffolds, creating each resource of your > > application and each important thing of the app (comments, posts, > members) > > you''d define in models. You would design your views, use some gem for > > authentication.. basically it. > > > > I think that´s it, basically. I tip I can give you is start making > something > > real, coding for sure :D .. in your free time, address some project you > have > > in mind and with no pressure or compromise, start developing it! > > > > Oh, and don''t forgethttp://railscasts.comI''ve already learned a lot of > > things with its screencasts! > > > > Cheers! > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.