⚠️ Fluidkeys is no longer maintained. This page is kept for posterity.
26 April 2019
Recap: Fluidkeys makes PGP simple for engineering teams. It helps you safeguard your source code and protect passwords, secrets and personal data.
In our desire to get v1 out the door, we’d neglected a little how Fluidkeys runs in the background. Each day it trys to run a task that checks if the key you made needs to be updated and extended, but discovered this wasn’t always working quite right on macOS.
To address this before it becomes a problem, we wanted to warn everyone who had made a key, but hadn’t got key maintenance working properly. We needed to let them know their keys would expire and what they could do about it!
Paul’s been beavering away the past couple of days, and from the pull requests I see him opening, it looks like he’s got it all working! 🙌
So not only will they all hear tomorrow, this’ll also happen automatically from now on.
It also means we’ve laid the groundwork for sending more helpful, automatic emails like this from Fluidkeys in the future.
Alongside warning people, I’ve been researching how we can use launchd rather than cron to schedule key maintenance on mac. We’ll get this into our next release, which will make this automated stuff so much more reliable, but more on that next week.
On Tuesday I pulled together an index page for the documentation we’ve been writing about Fluidkeys. It’s great getting this published!
I’ve enjoyed how writing docs have enabled us to deliver real minimum viable ‘features’! For example: deleting a team. In the future, we know that we need to build a command like
fk team delete, but in the meantime, instead of having zilch, we can spend an hour or so writing and publishing how to delete a team. Tada, people can now delete teams!
Lastly, we’ve got our shop in order by writing out a bunch of Trello cards for the next release. If you’re curious what we’re doing, you can check them out on our public roadmap!
Next week we’ll be doing as many of those cards as we can in preperation for releasing v1.1 on May 7th. Blimey, it’s nearly May already!
That’s all for now, see you soon.
All feedback is welcome, pop us an email to firstname.lastname@example.org