Reorganizate code using packwerk

app/controllers/home_controller.rb → app/packages/landing/controllers/home_controller.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
-class HomeController < ActionController::Base
+class HomeController < ApplicationController
   def index
   end
 end

app/packages/landing/package.yml

@@ -0,0 +1 @@
+enforce_dependencies: true

app/packages/rails/package.yml

@@ -0,0 +1 @@
+enforce_dependencies: true

config/application.rb

@@ -18,7 +18,7 @@ class Application < Rails::Application
     # Common ones are `templates`, `generators`, or `middleware`, for example.
     config.autoload_lib(ignore: %w(assets tasks))
 
-    config.paths.add "app/packages", glob: "{*,*/concerns}", eager_load: true
+    config.paths.add "app/packages", glob: "*/{*,*/concerns}", eager_load: true
 
     # Configuration for the application, engines, and railties goes here.
     #

config/database.yml

@@ -9,7 +9,7 @@ default: &default
 
 development:
   <<: *default
-  database: pictoplan_development
+  url: <%= ENV["DATABASE_URL"] %>
 
 test:
   url: <%= ENV["DATABASE_URL"] %>

config/routes.rb

@@ -1,12 +1,7 @@
 # frozen_string_literal: true
 
 Rails.application.routes.draw do
-  # Define your application routes per the DSL in https://guides.rubyonrails.org/routing.html
-
-  # Reveal health status on /up that returns 200 if the app boots with no exceptions, otherwise 500.
-  # Can be used by load balancers and uptime monitors to verify that the app is live.
   get "up" => "rails/health#show", as: :rails_health_check
 
-  # Defines the root path route ("/")
   root "home#index"
 end

docker-compose.yml

@@ -20,7 +20,7 @@ services:
     ports:
       - "3000:3000"
     environment:
-      DATABASE_URL: postgres://postgres:postgres@postgres/pictoplan_test
+      DATABASE_URL: postgres://postgres:postgres@postgres/pictoplan_development
     depends_on:
       postgres:
         condition: service_healthy

package.yml

@@ -1,11 +1 @@
-# This file represents the root package of the application
-# Please validate the configuration using `packwerk validate` (for Rails applications) or running the auto generated
-# test case (for non-Rails projects). You can then use `packwerk check` to check your code.
-
-# Change to `true` to turn on dependency checks for this package
 enforce_dependencies: true
-
-# A list of this package's dependencies
-# Note that packages in this list require their own `package.yml` file
-# dependencies:
-# - "packages/billing"

packwerk.yml

@@ -1,23 +1,8 @@
-# See: Setting up the configuration file
-# https://github.com/Shopify/packwerk/blob/main/USAGE.md#configuring-packwerk
-
-# List of patterns for folder paths to include
-# include:
-# - "**/*.{rb,rake,erb}"
-
-# List of patterns for folder paths to exclude
-# exclude:
-# - "{bin,node_modules,script,tmp,vendor}/**/*"
-
-# Patterns to find package configuration files
-# package_paths: "**/"
-
-# List of custom associations, if any
-# custom_associations:
-# - "cache_belongs_to"
-
-# Whether or not you want the cache enabled (disabled by default)
-# cache: true
-
-# Where you want the cache to be stored (default below)
-# cache_directory: 'tmp/cache/packwerk'
+exclude:
+- 'spec/support/**/*'
+- '**/lib/tasks/**/*.rake'
+- '{bin,node_modules,script,tmp,vendor,VENDORED_GEMS}/**/*'
+
+package_paths:
+- ./packages/*
+- .