You have to install Potassium globally:
$ gem install potassium
Starting a new project from scratch
potassium create command to create a new project:
$ potassium create <project-name>
- Potassium will perform a version check before running to ensure that you are using the latest potassium.
- If you feel that it's too slow, you may need to update rubygems:
gem update --system.
- Potassium uses node under the hood, so a check will also be performed to ensure you are running the supported version.
In case you want to use the Platanus Configuration you should use the following command:
$ potassium create <project-name> --platanus-config
This will create a project with the following configuration:
The remaining question will be asked as usual.
Running from Repository
If you cloned this repository and are running the gem using the bin script (
potassium/bin/potassium create), take careful note of the gem versions that are used. Sometimes the local Rails version is used instead of the one specified in the gemspec. Remove your local Gemfile.lock after pulling from the repository to help prevent these issues.
Adding recipes to an existing project
potassium install command to add a recipe to a project:
$ potassium install devise
You can force an already installed recipe by passing the
$ potassium install devise --force
You can run the command on its own to view all the available recipes and select one:
$ potassium install
What's inside Potassium?
Potassium Rails apps includes the following gems and technologies:
- dotenv for loading environmental variables in development
- Yarn for frontend assets packages
- EditorConfig for keeping all our editor configurations the same
- pry and pry-byebug for a less painful debugging experience
- RSpec for unit and integration testing
- FactoryBot for test factories
- Guard for continuous testing and other watch-related tasks
- AWS-SDK for file uploads, sdks, etc and because we use AWS
- Puma to serve HTTP requests
- Rack Timeout to abort requests that are taking too long
- Tzinfo-Data for updating timezone information
- Faker for creating development data
- Scout for monitoring performance
- Mjml for mails style
- Bullet to identify eager loading (N+1 queries)
The following optional integrations are also added:
- PostgreSQL or MySQL for the database
- Devise for authentication
- ActiveAdmin for admin interfaces
- ActiveAdminAddons for some help with ActiveAdmin
- Pundit for role-based authorization
- Sidekiq a simple, efficient background processing for Ruby
- Sidekiq-scheduler to run scheduled processes
- Mailing configuration for AWS SES and Sendgrid with recipient interceptor support
- Sentry to monitor exceptions and errors
- Vue.js or Angular 2 for frontend development
- Google Tag Manager for analytics
- Creates the Github repository of your choice for the project. A local git repository will always be created.
A few more things are added to the project:
- A low database connection pool limit
- Setup continuous integration in CircleCI to run tests
bin/setupscript to setup things on a newly cloned project
bin/cibuildscript to run continuous integration build on CI
db:fake_data:loadrake task to load fake data for development
The optional API support includes:
- Responders for dry-ing our api controllers
- Versionist for some flexible api versioning
- ActiveModel::Serializers for record serialization
- Simple Token Authentication for stateless API authentication
When you choose to deploy to heroku a few extra things are added for the project.
- Adds a Procfile to define the processes to run in heroku
- Setup continuous integration using docker and herokuish to maintain better parity between testing and production environments
- Adds a
bin/releasefile with the release phase script to run specific tasks before the app is deployed completely, for example
- Adds a
.buildpacksfile with the default buildpacks to use. It use the following buildpacks:
webpack based asset compiling
|to support the use of
.ruby-version file to instruct heroku which ruby version to use
|the base buildpack to run ruby applications
Also the heroku applications are created
- Creates a
- Creates a pipeline and assign the above application to the
- Setup initial configuration variables
- Set the application buildpack to the multi-buildpack
You'll need to manually
- Connect the pipeline with the github repository
- Assign a branch to each stage for auto deployments
- Enable deploy after CI pass
In order to CicleCI start building the project on each push you need tell circle ci. Go to https://circleci.com/add-projects, choose the repository from the list and hit Build Project
In order to enable code linting via CircleCI and ReviewDog, you need to activate the Only build pull requests option under the
Advanced settings section for your project.
Creating a new Test project from scratch
This is useful when you are adding new recipes to Potassium, and you want to use the
potassium create command, to check the new functionality without pain.
To achieve this you need to run, In the Potassium's root path, the
bin/potassium_test create instead of
potassium create command.
This command, will do the same as
potassium create but first:
- Will drop any existent database of the test app
- Will remove the directory containing a previous version of the test app
It's important to remember that
- Does not receive an
app_pathparam. It always creates the test project inside
- Can receive the same options as
- Runs with options with a default value. This is to avoid the "asking part" of the creation process. You need to enable what you want to test like this:
$ bin/potassium_test create --clockwork
On master branch.
Unreleasedtitle to current version in
- Commit new release. For example:
- Create tag. For example:
git tag v6.3.0
- Push tag:
git push origin v6.3.0
If you want to add functionality please go to the contributing
Thank you contributors!
potassium is maintained by platanus.
Potassium is © 2014 Platanus, SPA. It is free software and may be redistributed under the terms specified in the LICENSE file.