Meanwhile, I have a dummy ZIO project with a magnum aboard.
https://github.com/lvitaly/zio-tapir-example/blob/master/src/main/scala/com/lvitaly/api/repository/BookRepository.scala

@lvitaly Nice! Thanks

Some minor comments:

object BookRepository:
  val layer: URLayer[Transactor, BookRepository] =
    ZLayer {
        ZIO.serviceWith[Transactor](BookRepositoryLive(_))
    }

can be simplified with:

object BookRepository:
  val layer: URLayer[Transactor, BookRepository] = ZLayer.derived[BookRepositoryLive]

2. BookRepositoryLive class could be final (better for JIT)

🙂

@guizmaii, thanks! I knew there should be a simpler way to create such layers.

By the way, guys, if you have something particular in mind as an example, I would love to help you with it.

@lvitaly I think the missing example is a transaction in which the code throws an exception to revert it.
I have partially shown that in our talk

Hey, probably you know, but... The readme file and the presentation declare a ZIO module as magnum-zio, but in reality, it's actually magnumzio without the hyphen.

Readme:

"com.augustnagro" %% "magnum-zio" % "x.x.x"

mvnrepository:

"com.augustnagro" %% "magnumzio" % "2.0.0-M1"

Great work, thanks for taking this on @lvitaly . I'm happy to merge as-is, and we can create issues & iteratively enhance from there.

One thought I have (that we can address later) is that the example app be as realistic as possible. Since TestContainers should only be used for tests, it makes sense to strip that out and use an actual dockerfile with PG.

Going even further, I would like to see this become a g8 template that includes ZIO HTTP as well. I created https://github.com/AugustNagro/magnum-zio-http.g8 (empty g8 template)