This is a Rails application, initially generated using Potassium by Platanus.
Assuming you've just cloned the repo, run this script to setup the project in your machine:
$ ./bin/setup
It assumes you have a machine equipped with Ruby, Node.js, Docker and make.
The script will do the following among other things:
- Install the dependecies
- Create a docker container for your database
- Prepare your database
- Adds heroku remotes
After the app setup is done you can run it with Heroku Local
$ heroku local
The project is setup to run tests in CircleCI
You can also run the test locally simulating the production environment using CircleCI's method.
Style guides are enforced through a CircleCI job with reviewdog as a reporter, using per-project dependencies and style configurations.
Please note that this reviewdog implementation requires a GitHub user token to comment on pull requests. A token can be generated here, and it should have at least the repo option checked.
The included config.yml assumes your CircleCI organization has a context named org-global with the required token under the environment variable REVIEWDOG_GITHUB_API_TOKEN.
The project comes bundled with configuration files available in this repository.
Linting dependencies like rubocop or rubocop-rspec must be locked in your Gemfile. Similarly, packages like eslint or eslint-plugin-vue must be locked in your package.json.
You can add or modify rules by editing the .rubocop.yml, .eslintrc.json or .stylelintrc.json files.
You can (and should) use linter integrations for your text editor of choice, using the project's configuration.
To populate your database with initial data you can add, inside the /db/seeds.rb file, the code to generate only the necessary data to run the application.
If you need to generate data with development purposes, you can customize the lib/fake_data_loader.rb module and then to run the rake load_fake_data task from your terminal.
We are using the great Devise library by PlataformaTec
For managing uploads, this project uses Active Storage.
This project uses Power-Types to generate Services, Commands, Utils and Values.
To report our errors we use Sentry
We use:
- RSpec: the testing framework.
- Shoulda Matchers: one-liners to test common Rails functionality that, if written by hand, would be much longer, more complex, and error-prone.
- Factory Bot: a fixtures replacement with a straightforward definition syntax, support for multiple build strategies (saved instances, unsaved instances, attribute hashes, and stubbed objects), and support for multiple factories for the same class (user, admin_user, and so on), including factory inheritance.
- Faker: a port of Perl's Data::Faker library that generates fake data.
- Guard: automates various tasks by running custom rules whenever file or directories are modified. We use it to run RSpec when files change.
Place your unit tests inside the spec directory.
To run unit tests: bin/guard
We use, in addition to the previous gems:
- Capybara: helps you test web applications by simulating how a real user would interact with your app. It is agnostic about the driver running your tests and comes with Rack::Test and Selenium support built in. WebKit is supported through an external gem.
- Webdrivers: run Selenium tests more easily with automatic installation and updates for all supported webdrivers.
Place your system tests inside the spec/system directory.
To run system tests: bin/rspec --tag type:system
For hot-reloading and fast webpacker compilation you need to run webpack's dev server along with the rails server:
$ ./bin/webpacker-dev-server
Running the dev server will also solve problems with the cache not refreshing between changes and provide better error messages if something fails to compile.
For even faster in-place component refreshing (with no page reloads), you can enable Hot Module Reloading in config/webpacker.yml
development:
dev_server:
hmr: true