https://github.com/theogravity/feature-manager-wrapper
Edit: It looks like it's a backend replacement to LaunchDarkly, but you can still use the LD client from what I'm reading here, so there's nothing for me to integrate here.
https://github.com/theogravity/feature-manager-wrapper
Edit: It looks like it's a backend replacement to LaunchDarkly, but you can still use the LD client from what I'm reading here, so there's nothing for me to integrate here.
(https://github.com/github-community/community/discussions/77... - released by end of June)
Easy enough to separate them out of the rice after freezing too.
I resigned at 8 weeks of no pay, and couldn’t even legally force my company to give me a redundancy (3 years service) and I’m currently fighting to my right for 2 weeks notice pay (see note 1).
When you work for a startup you don’t have any rights to anything and you shouldn’t expect them to care about you.
Note 1: all this garbage is legal in Australia where all employee rights are hinged on insolvency and “hope for an investor” counts as not trading insolvent, which makes using your employees as creditors without their permission possible.
I’ve learnt my lesson about all of this. I will only work for established companies and I encourage anyone in the job market to think twice about signing with a company.. you need to be as confident in them for their responsibilities as they need to be in you.
Instead of using HSTS, you can also simply redirect any HTTP request to HTTPS. That way, you are certain that HTTPS is used, even if a browser does not understand HSTS.
With HSTS, once they've connected to the server over HTTPS once (e.g. at home), every connection from that browser will be immediately upgraded to HTTPS before even trying HTTP.
Your suggestion is valid - as HSTS is only delivered over HTTPS - and the upgrade is still required the first time.
See Firesheep for an example of how HTTP can be intercepted - https://en.wikipedia.org/wiki/Firesheep
- only share passwords for personal accounts; those accounts you terminate when the employee separates. For shared resources, use SSO and SCIM group management via the SSO provider to add and remove accounts from groups with different roles.
Rippling seems like a neat offering because they bundle SSO with HR people management, and their HR product is the best I’ve used as an employee - hopefully the administrative side is just as good or better.
If those SaaS tools aren’t in your budget, try looking for open-source or gratis alternatives with the same shape, or repurposing whatever IT infra you have to implement a similar model.
Happy to have a level of group synchronisation out of HR's systems, but certainly would not give them the ability to manage the high-power users.