Skip to content

kwstannard/engine_only_app_test

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

32 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Engine Only Test

I have a theory that it is possible and beneficial for large teams to have a single app for ease of development while at the same time maintaining separation of responsibilities by placing all code into gems and engines.

An alternate setup is to go the monorepo route and have all your apps in a single repo and then you don't need to worry about versioning your engines.

Setup

One of the engines uses postgresql, so install that first.

cd base_app
bundle install
rake engines:db:create
rake engines:db:migrate

You will see 3 migrations, but each migration is actually going to a different database.

Interesting tests

  • You can migrate and rollback individual engine databases.
  • You can drop and create the pg_engine database (sqlite doesn't drop dbs)

TODO

  • better base app dump solution. Schemas shouldn't change when running migrations in base app. Maybe delete dump from the base app migrations?
  • get authentication working
  • do some cross gem functionality

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published