Please enable JavaScript.

Coggle requires JavaScript to display documents.

Ruby on Rails (About (For Web Apps (A bit unique (Convention over Config,…

- - - - Convention over Config
      - "right" way
      - DRY
      - Independent of web server, also has own server for local dev
- - - - bundle install
        
        rails server
        
        webrick
        
        Installs shit from gemfile
  - - - config/routes.rb handles and sends the signal to
        
        the Controller
        
        to correct View
        
        Renders and returns html to browser
        
        <% messages.each do |message| %> iterates through each message in messages array. We created messages in the Messages controller's index action.
        
        For each message, we use <%= message.content %> and <%= message.created_at %> to display its content and the time when it was created.
        
        app/views/pages/home.html.erb
        
        A web template where you can loop thru data to show
        
        <% messages.each do |message| %>
        
        erb is a web template view
        
        Pulls from models and puts variables into play for the view
        
        rails generate controller xxx
        
        def index messages = Message.all end
        
        https://www.codecademy.com/articles/standard-controller-actions
      - add a rout in the file, creates what view the url points to
        
        get 'welcome' => 'pages#home'
        
        get '/tags/:id' => 'tags#show', as: :tag
      - rails generate model Message
        
        app/models/message.rb
        
        migration file in db/migrate/
        
        rake db:migrate updates the database with instructions and rows
        from here
        add a row with a variable
        
        t.string :title
        
        db:seed seeds with sample data
        
        n the model files, we used the methods has_many and belongs_to define an association between Tag and Destination:
        has_many :destinations denotes that a single Tag can have multiple Destinations.
        belongs_to :tag denotes that each Destination belongs to a single Tag.
      - TURN 1
        In the first turn of the request/response cycle, the page with the form is displayed to the user.
        A user opens his browser, types in a URL, and presses Enter.
        When the user presses Enter, the browser sends a GET request for that URL.
        The GET request hits the Rails router (config/routes.rb). The router maps the URL to the correct controller action to handle the request.
        The action receives the GET request and passes it on to the view.
        The view renders the page as HTML.
        The controller sends the HTML back to the browser. The page loads and the user sees the page with the form.
        TURN 2
        When a user submits the form, it triggers the second turn of the request/response cycle, where the submitted data is saved into the database.
        The user fills in the form and submits the form.
        When the user submits the form, the browser sends a POST request to the Rails app.
        The POST request hits the Rails router. The router maps the POST request to the correct controller action.
        The action receives the POST request. The action retrieves the submitted data from the form, and uses the model to store the data into the database.
        The model completes its task.
        The controller action passes the request on to the view.
        The view renders the page as HTML.
        The controller sends the HTML back to the browser. The page loads and the user sees it.
- - - - # or = begin to = end
    - - cust1 = Customer. new
    - - local start with letter or _
      - instance @
      - class @
      - global $
    - - def method() BODY end