In docker compose you can use `depends_on` [0] to define dependencies between containers and by default it will wait until a dependent container is "ready".

But you can also use a more verbose syntax to wait until a container is "healthy", as defined by its own healthcheck.

    services:
      web:
        depends_on:
          db:
            condition: service_healthy
      db:
        image: postgres

For example, in the case of PostgreSQL, there is already a tool called pg_isready [0] to do this inside a healthcheck as you described.

services: postgres-db: image: postgres healthcheck: test: ["CMD-SHELL", "pg_isready -U postgres"]

  application:
    image: image
    depends_on:
      postgres-db:
        condition: service_healthy

[0] https://www.postgresql.org/docs/current/app-pg-isready.html

I recently implemented a pivot table widget at work and it was mostly based on your code.

It was a while ago, but I remember it worked with very few changes.

    <link rel="alternate" type="application/rss+xml" title="XXX" href="https://blog.winricklabs.com/rss.xml">

Uh, this made me realize I forgot to add the RSS feed link to the head tag when I recently migrated my blog to Astro, fixed now!

https://kevincox.ca/2022/05/06/rss-feed-best-practices/

Compare how minio has advertised itself through the years:

2023: High Performance Object Storage for AI [0]

2022: High Performance, Kubernetes Native Object Storage [1]

2020: MinIO is a high performance object storage server compatible with Amazon S3 APIs [2]

I get that buzzwords and marketing are important, but it rubs me the wrong way

[0] https://web.archive.org/web/20230628165639/https://github.co... [1] https://web.archive.org/web/20220204012915/https://github.co... [2] https://web.archive.org/web/20200528195457/https://github.co...

https://web.archive.org/web/20190428005007/https://min.io/

There are some low hanging UX improvements you could work on next: tapping on a story in the feed shows options to go to the comments or to the article, and I wish this could be done with a single tap.

Similarly, when reading comment threads it’s a bit annoying having to open replies one by one. For me, the best threaded discussion reader on iOS is Apollo which shows quite a few replies and goes more than 6 levels deep with indentation without having to tap anywhere.

I can already tell you that the default font size is going to be divisive, especially for readers of HN ;)

I’ll keep this app around and check the change logs to see if it could replace Octal, which I’m using now

> the best threaded discussion reader on iOS is Apollo

Nested comment design have been a weakness of mine and it certainly shows in Hazumi. I want to revamp comments so badly, showing a batch of nested comments in one tap or by default does sound better. A general theme I've been hearing here is "less taps to get to the content the better". 100% noted!

> the default font size is going to be divisive

I ended up using the default `body` size from SwiftUI but if you mean it would be more appealing if smaller, then I could add a text sizing slider to the settings.

Thank you again for trying out Hazumi and giving your feedback!

Primarily since we syndicate the feed to Planet Postgres, and video would go against the rules. I'll see if we can split up our feeds somehow.

What I like the most is the Games page where I showcase my collection of board games with play statistics from BoardGameGeek.

Edit: to import games from BGG into Gatsby I wrote a source plugin which is open source https://github.com/TommasoAmici/gatsby-source-bgg