This is a step by step guide to creating new Ruby on Rails projects using Hix on Rails application template.
Follow the steps below to quickly get the fully-featured Ruby on Rails application ready for the business logic in no time.
Let's get started.
Before launching the installer, please follow the steps below.
For your convenience, Hix on Rails recognizes the environment variable
HIX_ON_RAILS_ACCESS_KEY, so if you don't want to copy and paste it every time you run the installer, you can export it from your command-line profile.
Open your shell script file for editing:
$ vi ~/.zshrc # or $ vi ~/.bashrc # or $ vi ~/.bash_profile
and paste the following code, with previously purchased access key.
Save the file and in the same command line, run
$ source ~/.zshrc # or $ source ~/.bashrc
Hix on Rails respects all possible
rails new configuration flags. For example, if you pass it the
--database postgresql flag, you won't be asked to select the database in the configuration wizard.
rails new project_name -m https://hixonrails.com/template.rb
After the initial Ruby on Rails installation run, the Hix on Rails wizard starts. All you need to do is select and/or input previously prepared prerequisites when asked for.
If you decided to use Coveralls, an additional setup compatible with the Continuous Integration provider of your choice is required - follow the instructions for services officially supported by Coveralls.
Your new Ruby on Rails project was set up for the business logic to be written. No more development configuration required.
Simply enter the newly-created directory with your Ruby on Rails project and run
Depending on what you've chosen, a lot of different, good stuff happened. Here's the summary of possible combinations that are not obvious from the options selected.
No matter what you chose, the dotenv-rails gem was installed, and the .env file was created, with defined variables related to your chosen setup.
The Ruby on Rails .gitignore file was created, based on the most popular template available.
If you chose to use RuboCop, the full suite of RuboCop gems was installed and configured in the .rubocop.yml file: rubocop, rubocop-performance, rubocop-rails. If you chose RSpec, the rubocop-rspec gem was installed, too.
If you chose Sidekiq and RSpec, the rspec-sidekiq gem was installed for testing your async workers.
If you chose Sidekiq with Sentry, there is an app/workers/sentry_worker.rb worker dedicated to sending the exceptions reports to Sentry asynchronously. It has its own default priority Sidekiq queue, called
Ruby on Rails project configuration is boring, yet crucial for the best development and maintenance experience.
Gems and tools configuration is not something that anybody knows (or wants to know) by heart, hence it is easy to forget about stuff and regret it later.
Hix on Rails aims to automate as much of the process as possible. Thank you for using it.
If you encountered any problems or have an amazing idea for improvement of Hix on Rails, please contact us on firstname.lastname@example.org.