I have been wrenching on my Qubes 4.2.0rc5 system and I am pleased with the overall progress. Yesterday I had a conversation in Discord, took a screen shot of a bit of it, then figured out how to get it out of dom0 so I could forward it via Signal. A red letter day - that’s the first “work” I’ve done using the system.
I built a template that has my usual stuff in it:
As I dislike and distrust Discord, I put it in a qube all by itself where it can’t cause any trouble. After a short time I realized Authy should have the same isolation treatment. Overall this is going good.
But now I come to Dropbox. I use this over all the other cloud file sharing things because it runs on every platform, behaves on headless Linux, and the only trouble it gives is the extraordinarily chatty local sync. Normally any major effort of mine gets a dedicated email protected with Authy, a Dropbox, and previously I’d make a VirtualBox VM for the job.
Dropbox on Debian distros as a service is very easy - you just need a service file for systemd, looks like this.
All the binaries go in ~/.dropbox-dist, so this fits into an AppVM, but I’m not seeing how to make it persistent with the start of the qube. Right now it’s running from command line under tmux, which isn’t the worst thing, but I want this setup to be as slick as my existing desktop.
Any hints on how to accomplish this the Qubes way?