• 1 Post
  • 75 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle






  • Where possible I think E2EE should be the default. So if you want to collaborate on documents you have to explicitly check a box that might say, “By checking this box I understand that I am opting into additional features at the cost of encryption.”

    I think encryption should be at the core of this project because it (1) protects the admins from some liability if/when a breach occurs and (2) the whole point of trying to get away from Google and similar hosts is to keep them from using our own data against us.














  • I don’t think it necessarily needs to be either or. Organizing the playbooks and folders myself can be stressful so an extra layer of organization might work best for you. There are other tools like Semaphore that are specifically built for Ansible executions though. Might need a lot of duct tape for Jenkins to run Ansible.

    And if you’re not a fan of yaml you can always nope out and embed shell scripts into your Playbooks. You can even put Docker compose yaml inside a playbook but it’s a bit inception-y and I don’t really recommend that.