Skip to content

Configure as a Heroku App #1

Description

@hopeseekr

OK, I know. I know! It's so 2007-late, but if the instructors want it, the instructors get it.

This app needs to be deployed to heroku.

Unless their stack changed, that means:

  1. Make it dockerizable.
  2. Only 1 monolithic Docker container for Web + CLI tasks.
  3. Very limited Redis/memcache (due to Heroku being SUPER expensive!!)
  4. Be careful with Database size (due to expense).

For the record, you can get better performance for 1/20th the cost via a $20 vultr.com VPS.

Yeah, I'm not a heroku fan. at all.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions