-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
self-host init database failed #26
Comments
@ninehills The commit e36e498 solved the issue. Please Update Repo and try again. |
I have already used the latest version, but it still gives that error. |
@ninehills I apologize for suggesting that it was fixed in the first place. My mistake!. The error appears to be occurring at line number 144 in the setup-dump.sql file. This might be because the public.app_user table hasn't been created yet. You can check the specific code snippet here |
This worked for me :
|
@Igosuki that works for me, just had to add quotes around user however, there is still something missing: column "profile.team_owner". I had to remove from the query in the code to make it work |
@Igosuki Thanks for suggesting "public"."app_user" table which is missing in setup_dump.sql table. |
Hi @prazevj, The correct table definition for create table "public"."profile" (
"id" uuid not null,
"updated_at" timestamptz,
"email" text,
"name" text,
"plan" text not null default 'free' ::text,
"team_owner" uuid,
constraint "profile_id_fkey1" foreign key ("id") references "auth"."users" ("id") on delete cascade,
constraint "profile_id_fkey" foreign key ("id") references "auth"."users" ("id") on delete cascade,
constraint "profile_team_owner_fkey" foreign key ("team_owner") references "public"."profile" ("id"),
primary key ("id")
); We'll make a cleaner database schema next week. We'll make sure to always keep |
@hughcrt Thank you. It would be great if we can have a clear and cleaner self-host steps. While using the self-hosted version in the callback handler code this URL is giving me Internal Server Error. I tried changing the Note: Hosted on Supabase (Self-Host) |
I can confirm the above issues (initial SQL not working, requires fixes discussed above) plus the following
I can help testing a new version but can't really help with development |
Hi guys! Apologies about those issues, we're currently fully focused on fixing some core issues with the python module and feedback tracking and will work on improving self hosting as soon as we have a bit more time on our hand.
|
I can't see a related env var in the template - there's only the ones for resend.com
This is the first one, all following fail the same way:
Result is a 406, the body contains: {
"code": "PGRST116",
"details": "The result contains 0 rows",
"hint": null,
"message": "JSON object requested, multiple (or no) rows returned"
} My best guess is that the initialization with the first user is not working as intended. After resetting everything and retrying, in supabase there is an account under "authentication" but all the tables are still empty. So the initial setup click flow is not actually creating a user in llmonitor, just the supabase auth entry. My first guess is that is silently fails somewhere e.g. because the DB schema is not correct. my vercel logs are empty. For me: pausing this until there is a reliable DB schema setup script that does not make the app fail. |
Hi,
Please let me know if it works for you! |
Use Supabase SQL Editor to run
setup-dump.sql
, then failed with follow message:file: https://raw.githubusercontent.com/llmonitor/llmonitor/main/selfhosting/setup-dump.sql
The text was updated successfully, but these errors were encountered: