Deploying Nova 4 via Envoyer #4558
-
I'm having difficulty deploying Nova via Laravel Envoyer, on a host managed with Forge. To authenticate the Nova installation there are two mechanisms: one to allow composer to download the package, and a second to enable the package license in Laravel. The first is meant to be managed via an The second location for Nova credentials is in a Annoyingly, this means that while my app runs perfectly on localhost, and it's easy to deploy in CI, getting it to work on my staging and production systems seems unnecessarily difficult. Should I get Envoyer to read my How is this supposed to be done? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
I've got this working via a manual installation and a deploy hook script. I created the
and placed that before the stock "Install Composer Dependencies" step. |
Beta Was this translation helpful? Give feedback.
-
I not 100% familiar with Envoyer but I do believe you can store
Reference: https://getcomposer.org/doc/03-cli.md#global-options |
Beta Was this translation helpful? Give feedback.
-
In Envoyer, you can create a new hook to authenticate Nova: Something similar to this: |
Beta Was this translation helpful? Give feedback.
In Envoyer, you can create a new hook to authenticate Nova:
Something similar to this: