For sure. What can I add to the Serverless Laravel course to prevent this? I've not heard of anyone deleting S3s and obviously I don't want this to happen to anyone else. Was the infinite loop the only issue you experienced?
And don't get my wrong, I will continue to use Vapor soon.
This cannot stop me from using it ^^
Personally, I see two options here:
You could add a short video/notice about configuring billing alerts/budgets on AWS. If this will be lesson 0 in course series - it will prevent such situation, I think. Because all experiments will be controlled from the beginning.
Communicate somehow with Laravel team, and put some additional notices before deleting projects and inform the user that he needs to remove everything from AWS manually (and give information what should be removed)
Something like this!
Thank you for understanding me, Jack!
And a big thanks for all your work! ❤️
For sure. What can I add to the Serverless Laravel course to prevent this? I've not heard of anyone deleting S3s and obviously I don't want this to happen to anyone else. Was the infinite loop the only issue you experienced?
Yes. Only one issue...
And don't get my wrong, I will continue to use Vapor soon.
This cannot stop me from using it ^^
Personally, I see two options here:
You could add a short video/notice about configuring billing alerts/budgets on AWS. If this will be lesson 0 in course series - it will prevent such situation, I think. Because all experiments will be controlled from the beginning.
Communicate somehow with Laravel team, and put some additional notices before deleting projects and inform the user that he needs to remove everything from AWS manually (and give information what should be removed)
Something like this!
Thank you for understanding me, Jack!
And a big thanks for all your work! ❤️
I didn’t realize you had taken my course when replying to you originally. That means I have more work to do here. So I apologize for jumping the gun.
I’ll take this and see what I can do.