37 karma · joined January 14, 2020
The above post was also linked from the obligator project's GH readme
If you're demoing using https://openidconnect.net for example, set your Client ID to https://openidconnect.net
Likewise, your ClientID should match the url of the website you are using this to connect with.
This was mentioned in the GitHub readme too but didn't click until trying the demo
But yes you can modify objects and arrays of a constant, which is not great.
For a medium-to-large app, K8s should offset a lot of the operational difficulties. Also you don't have to use K8s.
Cloud is turn-on/turn-off, whereas on-premises you pay up front investment.
Here are all of the hidden costs of on-prem that folks forget about when thinking about cloud being "expensive":
- hardware
- maintenance
- electricity
- air conditioning
- security
- on-call and incident response
Here are all of the hidden time-consumers of on-prem that folks forget about when thinking about cloud being "difficult":
- os patching and maintenance
- network maintenance
- driver patching
- library updating and maintenance
- BACKUPS
- redundancy
- disaster recovery
- availability
Did you find shortcomings with that plugin?
I sense a lawsuit from Atlassian poised at Zepel incoming.
For reference:
The GitHub repo: https://github.com/camsjams/rust-coal
The Documentation: https://camsjams.github.io/rust-coal/
Who has access to each client's database? Is it audited? Is it encrypted at rest? I'm sure it is, but Config.ly would be wise to add this information to avoid fears.
Also you can store encrypted secrets in Git just fine, there are a number of methods to do so very safely.
With a slight difference, it works 100% in the browser, you can use it here: https://camsjams.github.io/mr-roboto/
But you need to store the output somewhere safe.