This gist assumes:
Please read the new and updated version.
Sendy is a self hosted email newsletter application that lets you send trackable emails via Amazon Simple Email Service (SES).
You can deploy Sendy on Heroku using the following instructions (I assume you've already installed the heroku toolbelt).
| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
Command Line
pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)pry -r ./config/environment.rb - load your rails into a pry sessionDebugger
Sendy is a self hosted email newsletter application that lets you send trackable emails via Amazon Simple Email Service (SES).
You can deploy Sendy on Heroku using the following instructions (I assume you've already installed the heroku toolbelt).
Express makes it easy to nest routes in your routers. But I always had trouble accessing the request object's .params when you had a long URI with multiple parameters and nested routes.
Let's say you're building routes for a website www.music.com. Music is organized into albums with multiple tracks. Users can click to see a track list. Then they can select a single track and see a sub-page about that specific track.
At our application level, we could first have a Router to handle any requests to our albums.
const express = require('express');