Could you share the script that you use to generate: ``` import { Prisma, PrismaClient, } from "

Could you share the script that you use to generate:

import {
  Prisma,
  PrismaClient,
} from "http://xxxxx/prisma-edge-deno/0.2.2/deno/edge.ts";

import {
  Prisma,
  PrismaClient,
} from "http://xxxxx/prisma-edge-deno/0.2.2/deno/edge.ts";

import {
  Prisma,
  PrismaClient,
} from "http://xxxxx/prisma-edge-deno/0.2.2/deno/edge.ts";

import {
  Prisma,
  PrismaClient,
} from "http://xxxxx/prisma-edge-deno/0.2.2/deno/edge.ts";

We could add it to the CLI and that would probably almost be sufficient

rubenfOP•7/4/23, 9:09 AM

it would require to use the CLI ans sync on db changes but that's doable I suppose

zsnmwy•7/4/23, 9:09 AM

Now I just only to need build the image base on the base image.
More jobs are done on the base image.

FROM xxx/prisma-db/prisma-data-proxy:latest

ARG PRISMA_VERSION="4bc8b6e1b66cb932731fb1bdbbc550d1e010de81"
ENV OS="linux-musl"
ENV QUERY_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/query-engine.gz"
ENV MIGRATION_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/migration-engine.gz"

# install prisma
WORKDIR /app/prisma
# download query engine
RUN wget -O query-engine.gz $QUERY_ENGINE_URL && \
    gunzip query-engine.gz && \
    chmod +x query-engine
# download migration engine
RUN wget -O migration-engine.gz $MIGRATION_ENGINE_URL && \
    gunzip migration-engine.gz && \
    chmod +x migration-engine

ENV TZ Asia/Shanghai
RUN apk add alpine-conf tzdata tini --no-cache && \
    /sbin/setup-timezone -z Asia/Shanghai && \
    apk del alpine-conf

WORKDIR /app

COPY ./prisma ./prisma
COPY ./wait-for-it.sh .
RUN chmod a+x ./wait-for-it.sh

ENV MIGRATION_LOCK_FILE="/app/prisma/migration.lock"
ENV QUERY_ENGINE_PATH="/app/query-engine"
ENV MIGRATION_ENGINE_PATH="/app/migration-engine"
ENV PRISMA_SCHEMA_FILE="/app/prisma/schema.prisma"

EXPOSE 4466
CMD ["/app/main"]
ENTRYPOINT [ "tini", "--" ]

FROM xxx/prisma-db/prisma-data-proxy:latest

ARG PRISMA_VERSION="4bc8b6e1b66cb932731fb1bdbbc550d1e010de81"
ENV OS="linux-musl"
ENV QUERY_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/query-engine.gz"
ENV MIGRATION_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/migration-engine.gz"

# install prisma
WORKDIR /app/prisma
# download query engine
RUN wget -O query-engine.gz $QUERY_ENGINE_URL && \
    gunzip query-engine.gz && \
    chmod +x query-engine
# download migration engine
RUN wget -O migration-engine.gz $MIGRATION_ENGINE_URL && \
    gunzip migration-engine.gz && \
    chmod +x migration-engine

ENV TZ Asia/Shanghai
RUN apk add alpine-conf tzdata tini --no-cache && \
    /sbin/setup-timezone -z Asia/Shanghai && \
    apk del alpine-conf

WORKDIR /app

COPY ./prisma ./prisma
COPY ./wait-for-it.sh .
RUN chmod a+x ./wait-for-it.sh

ENV MIGRATION_LOCK_FILE="/app/prisma/migration.lock"
ENV QUERY_ENGINE_PATH="/app/query-engine"
ENV MIGRATION_ENGINE_PATH="/app/migration-engine"
ENV PRISMA_SCHEMA_FILE="/app/prisma/schema.prisma"

EXPOSE 4466
CMD ["/app/main"]
ENTRYPOINT [ "tini", "--" ]

Rrubenf Could you share the script that you use to generate: ``` import { Prisma, Pr...

zsnmwy•7/4/23, 9:12 AM

I can write a detailed guide to help you.
It needs two repo to show you how to do it.

rubenfOP•7/4/23, 9:15 AM

I think I don't follow everything but:

Would love to build a guide to integrate prisma
Improve windmill so that we can improve the prisma experience

zsnmwy•7/4/23, 9:16 AM

Too many details. I just picked the important part to say.

zsnmwy•7/4/23, 9:18 AM

But Windmill needs the data proxy. No matter what kind of data proxy.

rubenfOP•7/4/23, 9:18 AM

Agreed, even for the native sql integration we lose so much performance on establishing the connection

rubenfOP•7/4/23, 9:21 AM

I will probably strongly recommend using pgBouncer for postgres

rubenfOP•7/4/23, 9:22 AM

(That's for the user scripts, windmill uses of postgres already uses efficient pooling)

zsnmwy•7/4/23, 9:27 AM

Prisma has a good user experience.
How about both support?
Now I make Prisma work with a self-host data proxy in Windmill.
May just need little jobs to integrate with Windmill.

rubenfOP•7/4/23, 9:28 AM

the data proxy is always gonna be a long-runnin process which is something that should be decoupled from windmill

rubenfOP•7/4/23, 9:29 AM

that and the fact that it's gonna be very workspace/folder specific so you would need one such process per workspace

rubenfOP•7/4/23, 9:29 AM

that scale pretty terribly

zsnmwy•7/4/23, 9:32 AM

May need money to enable it on the online version.

zsnmwy•7/4/23, 9:33 AM

rubenfOP•7/4/23, 9:38 AM

I think it's more that there is only thing we want to do the devops of

rubenfOP•7/4/23, 9:38 AM

and that is windmill, not data proxy

MMeow the Magnificent Hello! I'm trying to programmatically disable buttons based on groups that ctx.u...

rubenfOP•7/4/23, 9:58 PM

Added groups to ctx on latest

rubenfOP•7/4/23, 10:13 PM

Not sure about willmind but yes that's pretty much the most common use-case for windmill

rubenfOP•7/4/23, 10:15 PM

I mena yes but for that use-case I would recommend self-hosting

rubenfOP•7/4/23, 10:15 PM

you can just set timeout to infinite

rubenfOP•7/4/23, 10:16 PM

it's one of the env variable of the workers

rubenfOP•7/4/23, 10:16 PM

I recommend reading the docs and README

Sindre•7/5/23, 2:48 AM

https://www.windmill.dev/docs/reference#raw-payload

Meow the Magnificent•7/5/23, 9:41 AM

Hello again!
I just updated to CE v1.125.0-3-g87de386b and got into some error as below. Not sure if i bonked anything?

Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/tmp/windmill/wk-878bb5c817ee-5cQZL/0189256b-0ea8-3d44-e202-24ee4be54b25/wrapper.py", line 8, in <module>
from f.ID import addcomment as inner_script
File "/tmp/windmill/wk-878bb5c817ee-5cQZL/0189256b-0ea8-3d44-e202-24ee4be54b25/f/ID/addcomment.py", line 2, in <module>
import wmill
File "/tmp/windmill/cache/pip/wmill==1.125.0/wmill/init.py", line 1, in <module>
from .client import *
File "/tmp/windmill/cache/pip/wmill==1.125.0/wmill/client.py", line 7, in <module>
from windmill_api.models.whoami_response_200 import WhoamiResponse200
ModuleNotFoundError: No module named 'windmill_api.models.whoami_response_200'

Meow the Magnificent•7/5/23, 9:43 AM

It seems to only happens on scripts that I just updated today, scripts that were untouched runs fine.

rubenfOP•7/5/23, 9:43 AM

@meowthemagnificent will investigate but note that I did add groups to ctx in 1.125.0

Meow the Magnificent•7/5/23, 9:44 AM

Yes, thank you so much! Amazed by the quick turnaround!

Meow the Magnificent•7/5/23, 9:53 AM

only diff I can find is the dependencies lockfile with old scripts on windmill-api==1.122.0 and wmill==1.122.0

rubenfOP•7/5/23, 9:54 AM

what I am confused about is that: windmill_api.models.whoami_response_200 is in 125.0

rubenfOP•7/5/23, 10:11 AM

@meowthemagnificent i'm trying to reproduce your issue but I really cannot. I wonder if your windmill_api cached is not corrupted

Meow the Magnificent•7/5/23, 10:14 AM

whoami_respponse_200.py actually missing in 1.125/api/models

Meow the Magnificent•7/5/23, 10:15 AM

o_O

rubenfOP•7/5/23, 10:19 AM

I think your pip cache is corrupted:

ls /tmp/windmill/cache/pip/windmill-api==1.125.0/windmill_api/models/whoami_response_200*
'/tmp/windmill/cache/pip/windmill-api==1.125.0/windmill_api/models/whoami_response_200.py'
'/tmp/windmill/cache/pip/windmill-api==1.125.0/windmill_api/models/whoami_response_200_usage.py'

rubenfOP•7/5/23, 10:20 AM

I'm not sure how could this happen we run: pip installpip install under the hood

Meow the Magnificent•7/5/23, 10:21 AM

did I inadvertedly bonked up something?

rubenfOP•7/5/23, 10:22 AM

I think most likely your instance shutdown mid 1.125.0 pip install or you got a network failure. On our end, we should probably do byte verification before commiting to the cache

Meow the Magnificent•7/5/23, 10:25 AM

>_<

Meow the Magnificent•7/5/23, 10:28 AM

ok, i went into my workers and reinstall wmill & windmill-api

FROM xxx/prisma-db/prisma-data-proxy:latest ARG PRISMA_VERSION="4bc8b6e1b66cb932731fb1bdbbc550d1e010de81" ENV OS="linux-musl" ENV QUERY_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/query-engine.gz" ENV MIGRATION_ENGINE_URL="https://binaries.prisma.sh/all_commits/${PRISMA_VERSION}/${OS}/migration-engine.gz" # install prisma WORKDIR /app/prisma # download query engine RUN wget -O query-engine.gz $QUERY_ENGINE_URL && \ gunzip query-engine.gz && \ chmod +x query-engine # download migration engine RUN wget -O migration-engine.gz $MIGRATION_ENGINE_URL && \ gunzip migration-engine.gz && \ chmod +x migration-engine ENV TZ Asia/Shanghai RUN apk add alpine-conf tzdata tini --no-cache && \ /sbin/setup-timezone -z Asia/Shanghai && \ apk del alpine-conf WORKDIR /app COPY ./prisma ./prisma COPY ./wait-for-it.sh . RUN chmod a+x ./wait-for-it.sh ENV MIGRATION_LOCK_FILE="/app/prisma/migration.lock" ENV QUERY_ENGINE_PATH="/app/query-engine" ENV MIGRATION_ENGINE_PATH="/app/migration-engine" ENV PRISMA_SCHEMA_FILE="/app/prisma/schema.prisma" EXPOSE 4466 CMD ["/app/main"] ENTRYPOINT [ "tini", "--" ]

Could you share the script that you use to generate: ``` import { Prisma, PrismaClient, } from "

Similar Threads

Similar Threads

Similar Threads