This repository was archived by the owner on Sep 9, 2024. It is now read-only.
Disable Authentication or Implement StaticCrypt? #1075
Unanswered
SummittDweller
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a working StaticCMS instance that I ported from NetlifyCMS recently. It's great but my client, a non-profit, needs a $0 solution and running an auth server just for the CMS seems to be the most expensive part of the mix. I have a bare metal server setup so that editors can use the CMS "locally" there and it works, but changes or additions they make are not "published" to the local Git repo as I hoped they would be.
I'm also using StaticCrypt with this client's admin site and it works very nicely for $0, presumably because it's still purely static, no moving parts required to make the authentication work. So I'm wondering if it's possible to configure StaticCMS so there is NO authentication required, so that I might encrypt the CMS instance using StaticCrypt for another $0 implementation?
Note that there's no sensitive data involved in any of this, I just need the convenience of StaticCMS for my content editors, so I'm not too worried that StaticCrypt isn't considered super-secure.
Beta Was this translation helpful? Give feedback.
All reactions