Nohea
Nohea
Hi, i just tested this with a brand-new nhost.io app w/dedicated postgresql. I tried to install 2 extensions in a migrate script, but failed: ``` CREATE EXTENSION postgis; CREATE EXTENSION...
I blogged a bit on this topic, it may be helpful. I created my own form element components which access the parent's context, in order render $errors UX as well....
Update to my prior comment above ☝️: I found the reason for the different pg extensions was that i didn't delete my local db folder, letting the `nhost up` recreate,...
> I would love to be able to do PR like that. But I don't think I can. As soon as I have a second I'll try, maybe I can...
@onehassan very cool work. I'm reading thru the code. Is it the case that your examples all execute the Nhost client via kit server (SSR)? The Nhost session is authenticated...
confirmed. I got the error on a new install. After i did: ``` touch .nostr/settings.json npm run dev ``` ... it started up
never mind - i found the problem in src/utils/settings.ts it has to be settings.yaml , not .yml if i renamed the file, it runs