Forge Laravel Nova Deployment Fail

Laravel Forge deployment of Nova fails:

51/97 [==============>-------------]  52%Warning from nova.laravel.com: 

************************************************************************************
Unable to find Nova (Silver Surfer) license holder with the given email address: [].
************************************************************************************
    Failed to download laravel/nova from dist: The 'https://nova.laravel.com/dist/laravel/nova/laravel-nova-845062cbaba71af76a9e29580fba07525350d9b2-zip-ffdb23.zip' URL could not be accessed (HTTP 403): HTTP/2 403 
    Now trying to download from source
  - Syncing laravel/nova (4.22.2) into cache

 55/97 [===============>------------]  56%
 60/97 [=================>----------]  61%
 70/97 [====================>-------]  72%
 79/97 [======================>-----]  81%
 91/97 [==========================>-]  93%
 97/97 [============================] 100%
In Git.php line 478:
                                                                               
  Failed to execute git clone --mirror -- 'git@github.com:laravel/nova.git' '  
  /home/forge/.cache/composer/vcs/git-github.com-laravel-nova.git/' 

This unfortunate problem occurs because the login name you've used on the Laravel Nova website has changed.

Steps to fix:

1. Log into Nova and get the right username and license key. Copy/Paste both somewhere 'cause you'll need it.

Nova doesn't have long sessions or remember password. Real drag. Make no mistake, I love this software. But painful these things are just like NovaPackages.com

2. Read the Nova documentation about deployment. Good luck with this.

A. contradics B.

A.

To avoid manually typing these credentials, you may create a Composer auth.json file while using your license key in place of your password:

bash

composer config http-basic.nova.laravel.com your-nova-account-email@your-domain.com your-license-key

B. 

Authenticating Nova in CI Environments ​

It's not recommended to store your Composer auth.json file inside your project's source control repository. However, there may be times you wish to download Nova inside a CI environment like CodeShip. For instance, you may wish to run tests for any custom tools you create.

Now what now if you're using Forge?

Googling site:nova.laravel.com forge gives zero results. Alas, deployment hell coming up.

So this is how I did it:

1. Follow the 1st set of instructions you're not supposed to follow because you're using source control.

2. Get the damn thing on forge.

3. Remove the file from source control.

4. Manually add the file to source control.