[–] 6 points 8 months ago*

What's the point in encrypting user data in transit if you're just gonna leave it unencrypted at rest??

Basic HTTPS does the trick of encrypting transfer, easy as fuck to set up, does not mean the app is any more secure tho.

Database encryption is usually not necessary if it is kept on a private network. Setting up sensible auth is usually enough. They kept some doors unlocked, tho.

  • source
  • parent
  • context
  • [–] 1 point 8 months ago*

    Sadly, the answer can range from super technical to super boiled down version. Depending on individual's knowledge, money reserves, and the will to set things up the proper way.

    Here's the boiled down version: You will need a server with a public IP address, preferably a hostname. The server has have SSH access. Then it is whichever way is most convenient - direct install, docker, etc.

    I, for example, have a Scaleway + Cloudflare DNS for my server and run everything in Docker behind Traefik reverse proxy that automatically serves certificates.

    The price is about 15€ for the server per month, DNS is free, domain is under 20€ a year - although way cheaper ones exist.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago (1 child)

    Strange, postgres is usually not the one to die. My server is permanently running out of space, so I have to keep deleting shit, and my PG did not die once. On the other hand, my other very old server (not updated in 3 years) has it's PG die (and automatically restart) at least once a day.

  • source
  • parent
  • context
  • [–] 1 point 9 months ago

    It is always either that the license is not permissive enough, too many changes are required that upstream wouldn't merge and its would be hard to keep rebased, showing the world that they can be absolutely independent, or not having enough experience and experts for given stack. Maybe I missed some reasons, but that'd be all I think of.

    Either way, if it's open sourced our company might switch.

  • source
  • parent
  • context
  • view more: ‹ prev next ›