Change host provider

Open
#16 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, elixir
Domain
cloud, infrastructure

Research direction

The issue names no files, tests, or deployment entry point. Start by reviewing the existing Heroku deployment and the linked Phoenix Heroku limitations, then compare AWS, DigitalOcean, and Gigalixir for the expected growth. Done means an alternative provider is selected and the deployment scope is agreed.

Written by the indexing model from the issue text.

Description

discuss priority-5

From an MVP perspective Heroku is an easy way to deploy application and I think for a first step we should deploy with it.

Howerver there are some limitation using Heroku with Elixir/Phoenix (https://hexdocs.pm/phoenix/heroku.html#limitations):
image

So when the app will be used by more users we might need to find an alternative, AWS, DigitalOcean, Gigalixir?

Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.