• breakman
• cache
• check_docker!
• check_docker_compose_v2!
• check_docker_running!
• chewy_index
• chewy_reset
• container_bash_exec
• container_exec
• containers_information
• cron_start
• cron_stop
• docker_compose
• init_nvm
• log_puma
• log_server
• log_sidekiq
• print_methods
• prompt!
• puma_dev_start
• puma_restart
• puma_start
• puma_stop
• rails7_header
• rails7_ready
• rails7_startkit_greetings!
• rails_assets_precompile
• rails_db_migrate
• rails_db_prepare
• rails_install_gems
• reset
• restart
• restart_all
• rspec
• rspec_with_cov
• rubocop
• rubocop_fix
• setup!
• sidekiq_start
• sidekiq_stop
• start
• start_all
• start_all_containers
• status
• stop
• stop_all
• stop_all_containers
• system!
• turn_off_elastic_settings
• whenever_show
• whenever_start
• whenever_stop
• yarn_build
• yarn_install

For demonstration, education and maintainance purposes I use a bit unsusual approach to name some files.

I _UNDERSCORE and UPPERCASE some files and folders to move them on the top of a folder and to make them more visible and to highlight their importance.

Data

• All services' data related folders are placed in ./db
• All folders are UPPERCASED

./db
├── ELASTIC
├── PGSQL
└── REDIS

Configuration Files

• All services' configurations are placed in ./config
• All configs are _UNDERSCORED and UPPERCASED

./config
├── _CONFIG.yml
├── _PUMA.rb
└── _SIDEKIQ.yml

Initialazers

• All services' initializers are placed in ./config/initializers
• All files are _UNDERSCORED and UPPERCASED

./config/initializers/
├── _CHEWY.rb
├── _CONFIG.rb
├── _REDIS.rb
└── _SIDEKIQ.rb

As a user to own files and run Rails inside a container I use

user:group => lucky:lucky => 7777:7777

If you would like to run the project on a linux environment then:

• create group lucky (7777) and user lucky (7777)
• run the project with RUN_AS=7777:7777 option

For many years Rails gives you freedom to choose development tools. Different databases, different paginators, different search engines, different delayed job solutions.

It is great. But all the time you need to choose something and install it from scratch.

I think I did my choice about many solutions and tools.

I want to install my minimal pack of tools now and reuse my StartKit every time when I start a new project.

With Docker I can roll out my minimal application with all required preinstalled tools in minutes, not in hours or in days.

I didn't work with Rails last 4 or 5 years. I wanted to learn new approaches and techniques. I found that there is still no a simple way to setup a blank app with most popular tools.

So. Why not to make my own playground?

I use tools that I like or want to learn.

I use tools that I think are the most popular ones.

I'm not a DevOps, but I have a vision how to deploy this code to production.

Right now it is not described somehow. It is in my plans.

• Nginx
• Production roll up
• Action Cable Link