Skip to content

ArVerify/arverify-node

Repository files navigation

ArVerify Auth Node

Configuration

You have two options to set the AuthNode configuration:

  1. Set everything through config.json.
  2. Set everything using .env (will be used if no JSON file is present).

Both ways require the following variables. Note that all Google Auth related variables must be obtained from the ArVerify Organisation. You can access these credentials in the Discord channel.

config.json .env Example Description
googleClientID GOOGLE_CLIENT_ID ... The Google Auth Client ID.
googleClientSecret GOOGLE_CLIENT_SECRET ... The Google Auth Client Secret.
endpoint ENDPOINT https://example.com The endpoint where the AuthNode is hosted.
keyfile KEYFILE arweave.json The path to your Arweave keyfile.

Deploying to Heroku

You can run a node with Docker on any platform you like. For example, use the following commands to run an AuthNode in Heroku. Make sure that you have Heroku and Docker installed on your machine.

heroku container:login
heroku create arverify-[your_org_name]
heroku container:push web
heroku container:release web
heroku ps:scale web=1

To check if the application is working, run:

heroku open

Releases

No releases published

Packages

No packages published