mirror of
https://github.com/TracksApp/tracks.git
synced 2025-12-15 23:00:12 +01:00
Page:
Heroku
Pages
1and1
Apache tips
Cloudmailin integration
Contributors
Debian 6.0 minimal setup
Debian 8 installation FR
Development tips and tricks
Discussing new gui for tracks 3
Faster user interface and better tablet experience
GTD on Tracks
Heroku
How to contribute
Install Tracks 2.0 on Ubuntu 11.04 minimal setup
Install Tracks 2.0 on Ubuntu 11.04 with lighttpd
Install Tracks 2.1 on Ubuntu 12.04
Install Tracks 2.3.0 on Ubuntu 14.04 LTS on AWS with SSL support
Install Tracks 2.5 on Ubuntu 20.10
Install Tracks 2.5.1 on Ubuntu 20.04 LTS on AWS with SSL support
Installing Tracks 2.2.2 on CentOS 6.5 Minimal x86_64
Installing tracks from git on gentoo (ebuild)
Installing tracks on openshift and using mailgun to email todos to tracks
Keyboard shortcuts
MySQL tips
OpenShift
Staannoe's Docker image
Testing
Tips and tricks
Tools
Tracks hosting
Tracks on Heroku
Uberspace
Ubuntu bundler broken due to ruby thor dependency explanation and workaround
Update already installed Tracks on Ubuntu 21.04
Upgrade from 2.4.2 to 2.5.1 on AWS Ubuntu 18.04 LTS
Upgrading rails
log files locations
No results
3
Heroku
Can Edremitoglu edited this page 2015-12-02 14:58:28 +01:00
Table of Contents
Heroku
Installing Tracks 2.0 or newer on Heroku is fairly simple, here are the steps to get tracks working on Heroku (steps for a non-programmer...):
- Unpack the application (I used "git clone," but unzipping will do just fine).
- Configure your Tracks instance
- Navigate to
config/environments/production.rband change the cache settings to "false" (config.cache_classesremainstrue, whereasconfig.action_controller.perform-cachingis set tofalse) - Copy
config/site.yml.tmpltoconfig/site.ymland change its contents (documented by the comments)- You definitely want to change your secret token
- Your admin email should be updated
- You should decide if you want open signups (beware spam robots!)
- Once you're ready, you'll want to configure one of the mail providers
- Change the
Gemfileand- Replace the lines
gem "sqlite3", group: :sqliteandgem "mysql2", group: :mysqlwith a singlegem "pg" - Add a definition near the top for the version of Ruby (e.g.
ruby '1.9.3') - Add a line
gem 'rails_12factor'
- Replace the lines
- Create a file called
Procfilewith a single line that readsweb: bundle exec rails server thin -p $PORT -e $RACK_ENV - Run
bundle install
- Navigate to
- In the
.gitignorefile, comment outconfig/site.ymlby putting a hash (#) at the beginning of the line. - Add the created
site.ymlandGemfile.lockfiles to the git repository withgit add config/site.yml Gemfile.lockand commit everything withgit commit -a -m "Updated/add the site information and bundle additions for Heroku" - Create a Heroku app on the Cedar stack with
heroku create {NAME} --stack cedar-14where{NAME}is something you care about. Or leave it off and Heroku will pick one for you. - Run
heroku config:add BUNDLE_WITHOUT="development:test:selenium"so that only gems needed for production are installed on Heroku - Push the commit with
git push heroku master - Run the migrations on Heroku with
heroku run rake db:migrate - Open the application with
heroku open - Create your administrator user
If something goes wrong,
- try to follow Heroku's advice (rerun
bundle installif you modifyGemfile) - commit your changes
- push your repository back to Heroku