I’m learning RoR, I’ve read some tutorials (railstutorial for the first one),
but I’ve a problem to define the logic layout of the my first simple website.
The structure is:
When you go to mysite.com you see a welcome page with the signup form or the link for login.
If you signup or you login into the site, you are at mysite.com/dashboard and you see a list of your messages.
You can go to mysite.com/$username and you see a page with a form where you can write a message for the $username.
Stop. That’s it. It’s very simple, I know, but is for learning.
The problem is this: I’m new to MVC paradigm and I don’t know how structure the logic layout of my app. Of course there’ll two models: User and Message. But for controllers? And which functions in any controllers? Should I use scaffolding?
Please give me a help, I’m very confused.
Thank you.
As others have pointed out, your controllers contain the logic for your code and invoke views based on that logic by rendering or redirecting to pages. You can define whatever actions you want in your controllers, and then use routes to map a particular URL to a controller action. That being said, Rails gets a lot easier if you “go with the flow” and make some simple assumptions about the actions that could happen. Both your users and your messages represent rows in their respective database tables. There’s no much you can do to a row in a database table – you can Create it, Read it, Update it, or Delete it (CRUD). If you define your actions in terms of these four logical actions, Rails lets you generate some easy routes.
You can back into any URL schema that you want, but what you are describing is:
Each of these maps to a CRUD action that you should be defining in your controllers.
Agreed also with other advice to simply do a few more tutorials that will probably clear this up.