migrated db and defined Proj & Task relationship

app/helpers/articles_helper.rb

@@ -0,0 +1,2 @@
+module ArticlesHelper
+end

app/models/project.rb

@@ -1,2 +1,3 @@
 class Project < ApplicationRecord
+    has_many :tasks
 end

app/models/task.rb

@@ -1,2 +1,3 @@
 class Task < ApplicationRecord
+    balongs_to :project
 end

app/views/articles/index.html.erb

@@ -0,0 +1,2 @@
+<h1>Articles#index</h1>
+<p>Find me in app/views/articles/index.html.erb</p>

db/schema.rb

@@ -0,0 +1,26 @@
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# This file is the source Rails uses to define your schema when running `bin/rails
+# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
+# be faster and is potentially less error prone than running all of your
+# migrations from scratch. Old migrations may fail to apply correctly if those
+# migrations use external dependencies or application code.
+#
+# It's strongly recommended that you check this file into your version control system.
+
+ActiveRecord::Schema[8.1].define(version: 2026_01_26_072814) do
+  create_table "projects", force: :cascade do |t|
+    t.datetime "created_at", null: false
+    t.string "project_name"
+    t.datetime "updated_at", null: false
+  end
+
+  create_table "tasks", force: :cascade do |t|
+    t.datetime "created_at", null: false
+    t.string "status"
+    t.string "title"
+    t.datetime "updated_at", null: false
+  end
+end