Heroku accepts deployment from new project but not existing project [2:54am]

[frankcollins3]

piggybacking off #272 which was heroku rejecting deployment. Still a module not found issue to overcome but besides that.

attempting to do: minimum viability deployment with heroku since the heroku connection string is already interacting with graphQL & UI locally. 1) after setting up heroku deployment with heroku backend 2) deploy

error: this stackoverflow link helped solve the problem of #272: "heroku rejects deployment" https://stackoverflow.com/questions/38658038/why-does-heroku-fail-to-detect-node-js-buildpack

a new issue is created: 1) $5/month heroku DB on "luv-water-app" which rejects the deployment. 1.1) There is no psql on the new app that accepts deployment, 1.2) can see tail-chasing on create heroku, add $5 DB, fix by create new heroku project, and add DB again.

proposed approach: as described above, found a way to push project which is essentially creating successful link between github and heroku. Find a way to get the current repo with the current $5/month psql, to link with its repo. (plan on stack overflow)

[frankcollins3]

(hopeful) GG : https://www.geeksforgeeks.org/how-to-make-changes-to-the-application-deployed-on-heroku/ [3:00am]

[frankcollins3]

heroku still trying to connect to the deleted repo. [3:20am]

[frankcollins3]

https://devcenter.heroku.com/articles/nodejs-support engines: is mentioned, which didn't seem to be needed to fix #272 in which heroku rejects deployment. [3:57am🏹]

[frankcollins3]

also in issue #272: buildpacks and "no framework detected" one can have a buildpack set and no framework set. i was wrong [3:59am]

[frankcollins3]

this stackOflow might help. Seems more ready to upload new git, and transfer postgresDB.

https://stackoverflow.com/questions/29753366/heroku-transfer-db-from-one-app-to-another [4:30am]

// glad to have thought of this as well (use same psql conn string from other app) felt there to be greater separation of concerns by having the DB correspond to the app itself.

commands to do so therein the URL

[4:36am]

[frankcollins3]

!sidewaysThumb.emoji()=> 👍 no problem but bookmarking: repo on github has 1 MAIN branch. "git push heroku MASTER" doesn't work.

👍 the new repo doesn't have a main branch so "git push heroku MASTER" does work.

[4:40am]

[frankcollins3]

bookmarking the simple idea of using github and connecting to the repository that's already there. reason this is more comfy now is that I've used a few heroku commands like: 1) clear connections. 2) set buildpack.

if connecting git is the fastest most efficient way it's not like using CLI has been completely dismissed. CLI has been used.

[4:47am]

while it's not deployed yet.. project proceeds through build steps w/ current existing repo, hence issue.close [4:53am]

[frankcollins3]

👍 the success of failure. Atleast the actual github repo and the present heroku deployment with $5/mo heroku DB sync

[4:55am]