Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
GeorgeMac
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
ReplayHouse – Turn ClickHouse into a reinforcement learning replay buffer
(jaymebrd.github.io)
3 points
by
GeorgeMac
1mo ago
|
0 comments
2.
▲
by
GeorgeMac
2y ago
I appreciate you sharing your first interpretations! I get the impression it’s not that clear what this is. Trying to position what this is / figure out where we go with it is tricky/going to be a journey. While this is in the CI
3.
▲
Show HN: Glu – Deployment pipeline framework as code
(github.com)
3 points
by
GeorgeMac
2y ago
|
2 comments
4.
▲
by
GeorgeMac
2y ago
Love this, and definitely where we're going. We already support S3, Azure and GCS, as well as OCI (any compatible registry) as a source in the open-source server-side evaluator. So if you pop a deploy step to any of these sources from
5.
▲
by
GeorgeMac
2y ago
You're not wrong there at all. That is a very reasonable assumption and I think the default behaviour with most early CD pipelines. Every commit leads to a deploy event. However, this can be changed, so that not all commits/pushes
6.
▲
by
GeorgeMac
2y ago
On this, we support publishing the state to object storage (S3, Azure, GCS) and to OCI as well in Flipt. Flipt Open-Source can be run to consume from these locations. You can go as far as configuring a workflow to publish on push, so that y
7.
▲
by
GeorgeMac
2y ago
Thats a great idea! I hadn't thought of combining it with a schedule for when a change is readable.
8.
▲
by
GeorgeMac
2y ago
Full version control, which can be collocated with other configuration for the rest of your system (thinks terraform or k8s manifests) means it becomes easier to build a picture of how your system was configured at a given point in time. Be
9.
▲
by
GeorgeMac
2y ago
Complexity of initial implementation was certainly one, as we developed it. It’s not the most well trodden path for this kind of problem (well trodden for other kinds of apps). Obviously it lacks things like relations and schema, that we ha
10.
▲
by
GeorgeMac
2y ago
Feature flag state is still served dynamically through Flipt. Your code doesn’t have to redeploy for the changes to “become live”. That’s the main benefit. Means you can experiment and target different cohorts with variants of your app with
11.
▲
by
GeorgeMac
2y ago
Flipt itself is open source and includes the git backend. So if that works for you, great! In our experience a lot folks came and said… but the ui is so important for us to be able to use a feature flag tool.
12.
▲
by
GeorgeMac
2y ago
This is actually how it works. Flipt is live tailing the repository and serving this dynamically to the clients. The repo with flag configuration can be solely for flags, or alongside other infra configuration on in more of a monorepo. You
13.
▲
Shipping Fast Without Breaking Things
(blog.flipt.io)
3 points
by
GeorgeMac
2y ago
|
0 comments
14.
▲
Authorization with Open Policy Agent
(blog.flipt.io)
3 points
by
GeorgeMac
2y ago
|
0 comments
15.
▲
So We Built a Reverse Tunnel in Go over HTTP/3 and QUIC
(blog.flipt.io)
4 points
by
GeorgeMac
2y ago
|
0 comments
16.
▲
by
GeorgeMac
2y ago
Amazing! There really is an awesome- for everything haha. Definitely checking these out.
17.
▲
by
GeorgeMac
2y ago
This is very cool. Checking it out! Thanks!
18.
▲
by
GeorgeMac
2y ago
This is great! Thanks for sharing!
19.
▲
by
GeorgeMac
2y ago
Would love a feature request GH issue for that! Seems totally doable!
20.
▲
Etcd and Concurrency STM
(george.macro.re)
3 points
by
GeorgeMac
3y ago
|
0 comments
21.
▲
Feature Flags and OCI
(flipt.io)
3 points
by
GeorgeMac
3y ago
|
0 comments
22.
▲
Ask HN: Do you use an external service for application configuration?
6 points
by
GeorgeMac
3y ago
|
0 comments
23.
▲
by
GeorgeMac
3y ago
Nice. Have you had to develop any capabilites around knowing what changed, when and by whom? i.e. audit log or so on? Just wondering what is your process in an incident when you want to know what changed in the system? e.g. so you can corre
24.
▲
by
GeorgeMac
3y ago
Nice, cool to hear flags in conjunction with canary releases. Are your flags simply configuration stored in files that your applications read at runtime? Then you push those updates out with Salt?
25.
▲
by
GeorgeMac
3y ago
Nice, makes sense. No external feature flag solutions here then? Just leveraging your languages build tooling and changing behaviour based on an environment key?
26.
▲
by
GeorgeMac
3y ago
Awesome, that’s makes total sense. Am I right in thinking the practices described here at Facebook are more like progressive delivery? As in, instead of adding code to call out to some external feature flag or configuration system, new chan
27.
▲
by
GeorgeMac
3y ago
Nice. Something home grown effectively then? What kind of application are you building with?
28.
▲
Ask HN: Do you commit feature flags to Git?
16 points
by
GeorgeMac
3y ago
|
13 comments
29.
▲
by
GeorgeMac
3y ago
Thank you Austin! I think I’ll update that with something like mermaid or d2.
30.
▲
Show HN: Cup – expose declarative APIs over config stored in Git
(github.com)
15 points
by
GeorgeMac
3y ago
|
2 comments
More ›