horse666
Joined 5 years ago
Karma
28
Submissions
25
Member since
Mar 17
Recent submissions
Comment · 10 months ago
Comment · 10 months ago
Aurora clones are copy-on-write at the storage layer, which solves part of the problem, but RDS still provisions you a new cluster with its own endpoints, etc, which is slow ~10 mins, so not really practical for the integration testing use case.
Comment · 11 months ago
Related https://github.com/jdx/hk/, from jdx, the author of Mise.
Comment · 1 year ago
No worries, thanks!
Comment · 1 year ago
Nice work @jdxcode, this looks great.
Is there any functionality in this release that might help with or be useful in features for sharing Mise config/tasks _across_ repos?
And do you have any thoughts on that idea in general?
Comment · 1 year ago
I don’t understand what you mean, sorry. If you are manually copying a password, then you are not using passkeys? There is nothing to copy/accidentally leak with passkeys.
I guess it will be a while before passkeys are the _only_ option that websites accept
Comment · 1 year ago
Phishing protection? Unlike passwords, passkeys are bound to a domain.
Comment · 1 year ago
Great, thanks for confirming
Comment · 1 year ago
Hi @tudorg - do the Xata copy-on-write branches work like Neon in that you effectively get an isolated Postgres cluster, allowing you to test roles, extensions, creating/dropping DBs, altering schema & data of existing DBs, etc? I looked in the docs but it wasn’t clear to me.
Comment · 2 years ago
Obligatory mention of https://raindrop.io/
I switched from Pinboard a year or more ago after using it for many years, mainly because I found the iPhone app and integration (eg share feature, to save bookmarks) to be flaky.
Raindrop has been great - imported seamlessly from Pinboard and the iPhone and Desktop app work well for me.
Comment · 2 years ago
Until Neon can fix that, I found it on the Wayback Machine - https://web.archive.org/web/20240524181543/https://neon.tech...
Comment · 2 years ago
Yes, also definitely a big vote for Mise.
I’ve switched recently from asdf for managing language & tool versions and the ergonomics are much nicer (eg one command vs having to manually install plugins, etc., more logical commands) It’s also noticeably faster.
Regarding the env vars features, a couple of relevant Mise issues around people trying to integrate env var secrets using SOPS, 1Password, etc.
Comment · 2 years ago
I’d not heard of Neon, it looks interesting.
When you say “a copy-on-write version of your prod database”, from reading the docs, this includes both schema and data?
I couldn’t find anything on data anonymisation/obfuscation - how do you handle that?
Comment · 2 years ago
Exa is unmaintained, but there’s a maintained fork called eza - https://github.com/eza-community/eza
Comment · 3 years ago
I would suggest never doing that, because it makes it impossible, or at least very difficult, to:
1. Lint the code using ShellCheck, which IMO is essential for any shell
2. Run and test that code locally, or anywhere outside of the CI tool
It’s only marginally less convenient to externalise the code into a .sh file and load it in CI.
Obligatory mention of Neon (https://neon.com/) and Xata (https://xata.io/) which both support “instant” Postgres DB branching on Postgres versions prior to 18.