mathias21 / ktoreasy Goto Github PK

Current watch pattern from application.conf is not working. Need to check why.

Dear Sir

very thx your post https://medium.com/@math21/testing-a-ktor-server-part-i-route-testing-84f8e82454d7 & demo

i have QA

as the code

i can start a ktor server at normal mode ( src)

i look the test sourceSet

you craete a test demo

if i export " embeddedServer(Netty, port = config.port) {...}" as a class (Yes i want run ktor serve at Andorid or other JVM like)

how let us test this class at Test mode ? or how start embeddedServer at Test ?

THX

Dear Sir

very thx your demo

i also ref other demo

this one use extra config file : "application.$environment.conf"

if i run ktor server at android with the same config

do you know how load ?

because "ConfigFactory.load" base on ClassLoader

THX

https://github.com/samgarasx/ktor-webapi/blob/0a9b0c56879a00919d62fdd8b9933e2e45e6309d/src/main/kotlin/ktorwebapi/Server.kt#L15

I want to propose a BaseApi, which will handle querying of data:
fun <T> dbQuery(block: () -> T): T

Currently, this is handled in BaseController. See this line.

By doing this, Controller won't be concerned about transactions and 'how' the data is fetched. That part will be the API duty to provide the requested data.
I can make a PR for this.

Dependencies seem to be outdated. It could be interesting to bump them to newer ones.

First, thanks for the great reference to get into KTOR.

I have been stumbeling across these lines in the Dockerfile

# Creating user
ENV APPLICATION_USER 1033
RUN adduser -D -g '' $APPLICATION_USER

Is there any specific reason you choose to run the application with a different user (other than not running containers as root)?

I'm working on a Multi-Secret-Santa side-project. I'm not sure if your familiar with the concept, but basically a group of people are secretly assigned another member of the group to give a gift at Christmas. The problem with that was that when last year multiple families got together to do their secret santa thing, they all happened to be given members from their own family. It's not a huge problem but it sort of defeats the purpose of it.

So my goal is to build a secret-santas matcher to mitigate the above problem. I've created a DB diagram with a bunch of junction tables: https://dbdiagram.io/d/616c66dc940c4c4eec9968d9

The junction tables are used to allow a user to be part of multiple groups, and a group to have multiple users.

In summery:
User = User
Group = Group of people who are not supposed to be each other's secret santa
Party = Multiple groups.

Constraint:
A member of a group cannot be the secret santa of another member of the same group.

So, on to my question:

Where (and how) would I place the join selects in your architecture? I thought of putting it in the GroupAPI, but it doesn't quite feel right to have it at that level. Should I use it in the UsersGroupDao? But how would I make use of the UserDao and GroupDao to create the joins?

Any input would be greatly appreciated! In the mean time, I'm going to watch the videos you mentioned in my other issue :)