Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider replacing Heroku support with fly.io #466

Open
theskumar opened this issue Jan 17, 2023 · 0 comments
Open

Consider replacing Heroku support with fly.io #466

theskumar opened this issue Jan 17, 2023 · 0 comments

Comments

@theskumar
Copy link
Member

No description provided.

theskumar pushed a commit that referenced this issue Dec 20, 2023
Added fly.io template files for a deployable Dockerfile and Github
actions.

> Why was this change necessary?

Spin up a hosted development environment fast.

> How does it address the problem?

Adds fly.io as an optional deployment destination.

> Are there any side effects?

The local and dev Dockerfiles do not have the same configuration that
Fly.io expects. When deploying the `dev` Dockerfile, Fly.io deploys hang
due to the `entrypoint` script running the gunicorn command which never
exits. Therefore a separate `compose/fly` folder has the necessary
changes to pass the build process.

Addresses #466

---------

Co-authored-by: Suneet Choudhary <suneet@fueled.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant