Well if you intend to use forge you'll need a provider so you might as well do that first. Digitalocean over Linode/Amazon for me.
Note any that you setup directly on the provider won't appear on Forge and can't be added later, they need to be setup initially through forge.
what is the process of updating on forge?
The default deploy script does this but you can modify it
git pull origin master
composer install --no-interaction --no-dev --prefer-dist
php artisan migrate --force
Either:
- Login to forge and hit the Deploy button for the site.
- Enable quick deploy button, so it'll listen on a branch and then trigger the deploy when code is pushed to it. Basically it'll ask for github/bitbucket and then copy over the trigger url as a hook for you.
- Use the 'Deployment Trigger URL'. ie if you use a testing service, you can add this to a successful build post hook. magnum-ci.com is ace.
If I was working by myself with 1 or 2 sites, I possibly wouldn't bother with forge and probably use http://capistranorb.com/. But $10 is nothing for the easy life.
Managing 20-30 sites with various certs and setups is a breeze with Forge, well worth the money. Never used envoyer