False

joined 2 years ago
[–] False@lemmy.world 4 points 1 week ago (1 children)

Why are they acting like Nextcloud is an alternative to AWS?

[–] False@lemmy.world 6 points 2 weeks ago (1 children)

I didn't say you were, I said you were asking about a topic that enters that area.

[–] False@lemmy.world 5 points 2 weeks ago (9 children)

You're entering the realm of enterprise AI horizontal scaling which is $$$$

[–] False@lemmy.world 16 points 2 weeks ago (2 children)

I thought I had a lot of RAM with 64

[–] False@lemmy.world 3 points 2 weeks ago* (last edited 2 weeks ago)

Import it into the trust store in the browser/OS. It should be the same (or very similar) operation for a self-signed cert and a CA that isn't subordinate to the standard internet root CAs.

If you can't import your own root CA cert then you're probably screwed on both fronts and are going to have to use certs issued by a public CA that's subordinate to a commonly trusted root CA.

My point here is that there's little distinguishing a self-signed cert and a cert issued by your own private CA for most people that are self-hosting.

[–] False@lemmy.world 2 points 2 weeks ago (6 children)

Trust the self signed cert. Works similarly to trusting a CA.

[–] False@lemmy.world 3 points 2 weeks ago (9 children)

Running your own CA is essentially still a form of self signed. Though it will work better for some use cases (at the cost of more complexity)

[–] False@lemmy.world 9 points 2 weeks ago

You don't need a public DNS record for https to work. You can just use public external certs as long as it's for a domain you own. You don't need to setup the same domains externally.

If you want certs for a domain you own, then yeah you're looking at self signed.

[–] False@lemmy.world 1 points 3 weeks ago (1 children)

You may be thinking like a programmer but the guy you responded to is thinking like a software engineer.