apps VS CapRover

Access token is the simple way to authenticate to the Rest API. You simply need to go to your GitHub account settings then Developer Settings (or simply go to this URI), and then create an access token. You can either choose the classic tokens (no restriction) or the fine-grained token where you can use fine-tuned permissions.

Go to the GitHub Apps and select to create a new GitHub App

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

When you're on https://github.com/settings/apps (GitHub Apps) there will be an action list button called "Personal access tokens".

In your Github Settings, go to Developer settings. Then, in Personal access tokens, Generate a new classic token with scope: write:packages

To create your GithubProvider ID and SECRET, navigate to your GitHub account developer settings and click on the OAuth Apps tab to register a new application.

Github project is needed to authenticate users. You may do so by visiting https://github.com/settings/apps. Note the Client ID and Client secret. Also, set two Callback URLs for project and contributor authentication.

In my previous post, I developed a GitHub App. I found the app at this location:https://github.com/settings/apps to edit it. In the Permissions and Events tab, I updated the user permissions and the events I wanted my app to subscribe to. In this case, I wanted my app to listen to and have access to when a user starred the repository.

Next we need to go to https://github.com/settings/apps/new to configure the integration. Fill the fields as follows:

Finally, I kinda wonder if CapRover is still alive. As I write this it has been over 60 days since there has been any activity on their GitHub.

https://github.com/caprover/caprover https://github.com/caprover/one-click-apps

Looks like Caprover https://github.com/caprover/caprover which has been around for a bit, have used in past. Any notable benefits over it?

CapRover's NGINX doesn't support sticky sessions (see this issue).

All the ways I've found imply dokku or caprover, to run docker for each separate app, Postgres, Redis. It's also so hard to even setup db backups (https://github.com/caprover/caprover/issues/158 https://github.com/caprover/caprover/issues/410).

You should definitely looking for Caprover. It has a really really big App Library. A demo is also available online.

Another possibility would be to use selfhosted caprover (https://github.com/caprover/caprover) for the Website Hosting. Leaves you still with the e-mail problem.