It’s been five months since my last post in this thread and I have learned a lot since then, so I can answer these myself now 
(but please correct me if I’m wrong):
As far as I know now, the database doesn’t change when you update a plugin so it’s fine to update your plugins locally and deploy them.[quote=“Twansparant, post:3, topic:4877”]
Not ALL your code in your theme folder. node_modules, assets, bower_components etc are not deployed right?
[/quote]
No they are not, but as long as your assets, package.json & bower.json are in a remote version control repository, then you can always recompile your dist, node_modules & bower_components locally.
Don’t think so, you don’t need it on the droplet since that already is a vm box.[quote=“Twansparant, post:3, topic:4877”]
Not sure if you are supposed to sync them too with Github?
[/quote]
Yes that is best practice. I have a separate private repo for my Trellis clone, and one for my Bedrock clone (including the Sage theme), but it’s recommended to have a separate Sage repo too, so you can update all three separately more easily.[quote=“Twansparant, post:3, topic:4877”]
Yeah but the database of your local project is ‘embedded’ in the local VM on that computer, so if you want to continue working on that project on a different computer, you can’t really unless you export/import right?
[/quote]
This is true, but I found a way to automatically import & export the database with Vagrant triggers and keep everything synced through dropbox: Keep database synced between computers in Trellis/Bedrock/Sage setup - #40 by Twansparant