Unclear docs, missing env variables and more... about envault HOT 2 CLOSED

Hi Paul, thanks for opening an issue.

We'll add a note about Composer to our installation guide. I apologise that it seems vague to you. In truth, a large majority of our users are Laravel developers so are familiar with the setup process, we've not run into much confusion before.

The database configuration included with Envault is taken directly from Laravel, as this serves as an appropriate setup for 99% of production environments. I'll modify the charset configuration to make sure that this is customisable through your .env, and will update you when this has been done.

Envault allows you to use any mail driver included with Laravel, as mentioned in our setup guide. To use Mailgun as you mentioned, you just need to add these keys to your production .env. It's simply impractical to include every possible configuration option in the default .env.example we provide, and this is why we have referenced the Laravel documentation several times throughout the setup guide; it provides a comprehensive overview of all of your options and how to use them.

To address your final point, you opened a support ticket and stated that you did not have much experience with deploying PHP applications, so you were finding it challenging. In response, we offered you an exclusive $10/month managed hosting service. We don't generally advertise this, as it's at-cost for us, so feel free to decline the gesture. We also suggested that you might want to try out services like Laravel Forge and DigitalOcean which make it incredibly easy to host Envault, but this costs more.

Please let me know if you have any further issues.

Kind regards,
Dan

from envault.

Hi Paul, thanks for opening an issue.

We'll add a note about Composer to our installation guide. I apologise that it seems vague to you. In truth, a large majority of our users are Laravel developers so are familiar with the setup process, we've not run into much confusion before.

The database configuration included with Envault is taken directly from Laravel, as this serves as an appropriate setup for 99% of production environments. I'll modify the charset configuration to make sure that this is customisable through your .env, and will update you when this has been done.

Envault allows you to use any mail driver included with Laravel, as mentioned in our setup guide. To use Mailgun as you mentioned, you just need to add these keys to your production .env. It's simply impractical to include every possible configuration option in the default .env.example we provide, and this is why we have referenced the Laravel documentation several times throughout the setup guide; it provides a comprehensive overview of all of your options and how to use them.

To address your final point, you opened a support ticket and stated that you did not have much experience with deploying PHP applications, so you were finding it challenging. In response, we offered you an exclusive $10/month managed hosting service. We don't generally advertise this, as it's at-cost for us, so feel free to decline the gesture. We also suggested that you might want to try out services like Laravel Forge and DigitalOcean which make it incredibly easy to host Envault, but this costs more.

Please let me know if you have any further issues.

Kind regards,
Dan

@danharrin - I'm new to Envault and I am not an active user of the Laravel framework. I would suggest that your documentation be made clearer for those that are not familiar with this model. I'm still not able to get past step 1 from the README. Getting the same error described by the OP. See #2 for more details.

from envault.