Nuts is now UNSUPPORTED

[hubdotcom]

The deploy to heroku button no longer works and this no longer runs on heroku

[AaronO]

@hubdotcom Can you be more specific and elaborate on what doesn't work ?

[hubdotcom]

Go here:
https://nuts.gitbook.com/deploy.html

Click Deploy to heroku

Nothing happens

[hubdotcom]

Also there are security PR's that are not being acknowledged. Is it possible to appoint a second maintainer?

[GitFlip]

@AaronO Is this still an issue? I clicked on the heroku button, filled out all the git information. I got to the project's overview on heroku, it says the build succeeded and that it has been deployed in the activity, but I do not see anything about "nuts" running, should I see that somewhere?

Also, if I go to my heroku application url all it says is "application error". Is that normal?

Pretty much, how do I know nuts is working?

Tagging @hubdotcom in case he now has this working.

[hubdotcom]

It works, it's just not being maintained by the developers

[GitFlip]

@hubdotcom Thanks for the reply, that's good to hear. Do you happen to know the answer to my question? Once I press the "Deploy on heroku" button, fill out form, and press deploy is nuts now working? I don't see anything in the overview that explicitly states nuts is running. Also like I said when I got to my heroku url I get "application error".

Thanks in advance!

[AaronO]

@GitFlip Check your heroku logs, you're maybe missing an ENV (config value)

[GitFlip]

@AaronO It looks like I have an ENV. See the log:

-----> Node.js app detected
-----> Creating runtime environment
       
       NPM_CONFIG_LOGLEVEL=error
       NODE_VERBOSE=false
       NODE_ENV=production
       NODE_MODULES_CACHE=true
-----> Installing binaries
       engines.node (package.json):  unspecified
       engines.npm (package.json):   unspecified (use default)
       
       Resolving node version 8.x...
       Downloading and installing node 8.11.1...
       Using default npm version: 5.6.0
-----> Restoring cache
       Skipping cache restore (not-found)
-----> Building dependencies
       Installing node modules (package.json)
       added 334 packages in 9.142s
-----> Caching build
       Clearing previous node cache
       Saving 2 cacheDirectories (default):
       - node_modules
       - bower_components (nothing to cache)
-----> Pruning devDependencies
       Skipping because npm 5.6.0 sometimes fails when running 'npm prune' due to a known issue
       https://github.com/npm/npm/issues/19356
       
       You can silence this warning by updating to at least npm 5.7.1 in your package.json
       https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version
-----> Build succeeded!
-----> Discovering process types
       Procfile declares types     -> (none)
       Default types for buildpack -> web
-----> Compressing...
       Done: 24.2M
-----> Launching...
       Released v4
       https://terraria-launcher.herokuapp.com/ deployed to Heroku

Or am I mistaken and there is some other log?

Edit: In my activity log it also says that I set these configs: Username@gmail.com: Set GITHUB_REPO, GITHUB_TOKEN, API_USERNAME, API_PASSWORD config vars

[raphaelschaad]

Regardless of the issue discussed here, Nuts does seem unsupported by now (3 years later)?

[GitMurf]

Crazy to me that Electron still officially lists this as one of the top options for auto updating! Very frustrating. Has anyone gotten this to work recently?

RE: electron/electron#29943