• 36 Posts
  • 98 Comments
Joined 2 years ago
cake
Cake day: July 17th, 2023

help-circle

  • I do this. Its great because of catchall emails and the ability to make one address per merchant. Then if a company leaks your email or gets hacked, you can simply change the email from hacked-company@domain.tld to hacked-company2@domain.tld and block the old address.

    It also is good for ownership as you said. If Tuta gets purchased by Google (for example), then you can simply pivot to any of the many other email providers and not rely on a company being not evil.










  • Not really. I also didn’t have much data in them, so I opted to start from scratch. I’d recomend searching for “service docker” to find how to run that thing in dockers compose. Then I make a folder for each thing. In my home directory, I make a new folder. Say fileBrowser. Then inside that I make docker-compose.yml and put the compose from the internet (if you find a docker run, you can convert it to compose via sites like composerizer). Then for config volumes I like to specify ./ so it goes to the current folder. I.e. ./filebrowserconfig/settings.json:/settings.json so that inside the fileBrowser folder we’re already in, it has a folder called filebrowserconfig and a file called settings.json. (note that docker tries to make folders, not files. So if the json file doesn’t already exist, it’ll make a folder named settings.json lol)



  • I used the owner profile. Idk much about it tbh, I have yet to do more in depth testing as my phone doesn’t have displayport functionality so I am a little discouraged to be an early adopter too. I couldn’t get SSH setup so typing a lot on the small keyboard wasn’t ideal.

    I’d check Google/GOS docs for more info for now. I’ll bet there’ll be a lot in the coming years as fast as usecases