rubenf
rubenf9mo ago

You can create your own resource types and uses it for anything. It's just a key value store where v

You can create your own resource types and uses it for anything. It's just a key value store where value are json object constrained by a resource type and its schema
9 Replies
rubenf
rubenfOP9mo ago
It might be a go issue, will investigate but in your case with shared directory on, the shared dir doesn't exist? @oldcat for go specifically, it's at ../shared
Unknown User
Unknown User9mo ago
Message Not Public
Sign In & Join Server To View
rubenf
rubenfOP9mo ago
It will be improved for go but it has nothing to do with the code you linked
Unknown User
Unknown User9mo ago
Message Not Public
Sign In & Join Server To View
rubenf
rubenfOP9mo ago
@oldcat fixed on latest @Hugo C. we need to investigate if the main function presence parser runs with generate-metadata
httpteapot
httpteapot9mo ago
I'm considering migrating a bunch of bun scripts to windmill to improve scheduling, testability, logging (they are currently deployed on Vercel alongside my web app, with an http endpoint to call them). I like that in local I can call my scripts like regular bun scripts. But I find that they are a lot of metadata files associated, like *.script.lock and *.script.yaml for each script. Wouldn't it be possible to group these metadata files, for instance in a .wmill directory (similar to .git), to expose a minimal file tree on local dev?
rothnic
rothnic9mo ago
I just had a script start failing all of a sudden and it seemed related to the sharp npm library. I didn't have a version specified for it, so not sure at the moment if it is related to a windmill version update, an update to the library, or what. I did see the suggestion about trying nobundle and that fixed it and it said to reach out when this happens. //nobundling const sharp = require('sharp'); is the beginning of the script
rubenf
rubenfOP9mo ago
Did you update windmill recently?
rothnic
rothnic9mo ago
checking with our admin, think he isn't quite in yet, but it happened in the middle of the night so I would think not. Will know for sure in a bit. We are currently on EE v1.396.1

Did you find this page helpful?