Dependencies

• Ruby 3.0

Configuration

1. Use the template and make sure to check "Include all branches"
2. Clone the repository to the local machine
3. Initialize git-flow in all local machines with git flow init
   1. Set production branch: main
   2. Set development branch: development
   3. Set the rest of the options as defaults
   4. Initialize a new feature branch. You can call it setup-from-template
4. Run bundle update to install the latest version of the gems for the project
5. Reinstall and setup the required packages by running bundle exec bin/setup
6. Generate the Rails credentials for the project: EDITOR=true bundle exec rails credentials:edit
7. Change the name of the project. Use the commit 324932f as reference
8. Execute the Rubocop command, so the linter's workflow won't fail: bundle exec rubocop -A
9. Add and commit all your changes
10. Finalize your feature branch and merge your changes
11. Everything should be ready to start working!

Note: all packages already set up, this includes: Devise, RSpec, Capybara, Factory Bot, Rubocop, GitHub Workflow, and it's ready to deploy to Heroku. Start to work with the models, views, and controllers. Note that you'll need to use the correct generators (i.e. bundle exec rails generate devise User).

Note: The development/test version will use SQLite3, but the deployed version will use PostgreSQL. The bundle command will install the pg gem anyway, and if it fails to set it up, install PostgreSQL even if never used or configured.

Important

1. Change the hostname for devise when deploying to Heroku, check the files inside config/environments