Update labels to the latest Heroku stack by 1 November 2020

[iteles]

https://help.heroku.com/SMQ1J712/cedar-14-end-of-life-faq

[nelsonic]

@iteles I strongly suspect that updating the stack will "break" the App as the underlying dependencies have breaking changes. (as noted in #92) I would recommend setting the dependencies to fixed versions in package.json instead of "greater than X" and having a package-lock.json file that reflects these working versions. LMK if you want to pair on this. 👍

[nelsonic]

Even though it's tempting to upgrade the stack as part of #95 (Heroku build fail),
we must resist the temptation because it the Cedar 14 instance has all the older dependencies (that work!), upgrading to Heroku-18 Stack for this app will force us to use Node 12 which will automatically download new versions of the dependencies ...
https://devcenter.heroku.com/articles/nodejs-support#supported-runtimes

Note: the only thing that doesn't work on my localhost, which is running Node v12.18.3 (latest), is shot which is required for testing ... #92 🤦

[nelsonic]

October 2021, The Heroku App is Still Working with the "Old" Stack:

https://label-sync.herokuapp.com/ basically, as long as we don't re-build/restart the dyno it just keeps working ...

https://github.com/dwyl/rbac/labels

But I just noticed that the descriptions don't sync for a repo that already has the labels ... 💭
So we will need to migrate this to Elixir/Phoenix at some point (so that it's easier to maintain than Hapi...)

We could just use https://github.com/dwyl/elixir-auth-github directly, however,
I have a strong preference for using auth and auth_plug because it abstracts away Auth elegantly.
(obvs that means we need to get Auth working again ... dwyl/auth#143 ... ⏳ P1 ... )

[SimonLab]

So we will need to migrate this to Elixir/Phoenix at some point (so that it's easier to maintain than Hapi...)

I'm thinking of creating a new repository for the Elixir/Phoenix label version (phx-labels or label-sync maybe?).
Creating a new phoenix project on top of the Hapi project will require a lot of cleanup later on.

[nelsonic]

Hi @SimonLab 👋
keen to maintain the existing contributors & context for the project. 💭

Please use the following branch as a starting point if you're thinking of tackling this task:
https://github.com/dwyl/labels/tree/migrate-to-phoenix-issue-%2394

Also, if you don't mind, please break down the task into sub-tasks with separate issues on GitHub with time estimates so that we can measure the time investment in this useful tool. Thanks!

[SimonLab]

Yes makes sense to keep track of what we have done so far 👍
I'm going to create an epic issue (and sub issues) to track the progress done to switch the project to Elixir.

[nelsonic]

For now we just want to replicate the existing functionality with tests.
If we can use auth.dwyl.com that would be great.
We don't want to store any PII and definitely no auth tokens on the labels server.
But it might be nice to track basic "sync" (usage) stats in a DB just so we have some history:

• Who authenticated to use the labels app
• Which source and target repos they synched between

Crucially we want the descriptions of existing labels to be updated and any new labels to be synched.
If we can record as much of a "dev log" as possible it will help with maintaining the project going forward.
Doesn't have to be a full tutorial like https://github.com/dwyl/phoenix-chat-example but good to have something.

[SimonLab]

The Heroku stack has been updated however we redirect the heroku application to https://labels.fly.dev/
see #110