Investigate how to migrate Hits App to Org (from Personal) on Fly.io

Open
#114 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
cloud, devops, infrastructure

Research direction

Start with the Fly.io setup guide and the linked Fly.io organisation usage page, then inspect how the Hits App is currently deployed. Done means the app is migrated from the personal account to the Hits organisation and team access is available for debugging.

Written by the indexing model from the issue text.

Description

chore enhancement help wanted priority-3 T1h technical

The default for Fly.io apps when following their setup guide is to create "personal" apps.
We want our Hits App to be in an Organisation so that we can grant access to the team.

see: https://fly.io/organizations/hits/usage

Not urgent as the App is working. But if we ever need someone else to debug something e.g. dwyl/hits#129 then it might be useful.

Dominant language
Shell
Stars
443
Forks
177
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/learn-devops

All issues in dwyl/learn-devops

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.