Does it have AI chat? If so how does it's infrastructure look like?
Can't the supabase team submit PR's for coolify?
The supabase service was recently updated. Probably best to stick with that and help contribute to coolify to add more patches in the future.
nice, that worked
ok, why have i not thought about this earlier, i could perhaps move this functionality to the frontend!
it may be supabase's biggest weak point
its not my first trouble with them
god why are edge functions so frustrating
what can I do at this point?
<@764524500162445402> I've tried to make the function as small as possible, but `import 'pdf-parse';` is taking up too much space
its only a bit above
yes
`index.ts` ```js import { RecursiveCharacterTextSplitter } from 'npm:@langchain/textsplitters'; import { PDFLoader } from 'npm:@langchain/community/document_loaders/fs/pdf'; import { DocxLoader } from 'npm:@langchain/community/document_loaders/fs/docx'; import { CSVLoader } from 'npm:@langchain/community/document_loaders/fs/csv'; import { TextLoader } from 'npm:@langchain/classic/document_loaders/fs/text'; import { PPTXLoader } from 'npm:@langchain/community/document_loaders/fs/pptx'; import { serve } from '../_shared/edge.ts'; import { GoogleGenerativeAIEmbeddingsWithDimension } from '../_shared/gemini.ts'; import type { Document } from 'npm:@langchain/core/documents'; import type { SupabaseClient } from 'npm:@supabase/supabase-js'; import type { ProcessDocumentRequest } from './types.ts'; import 'officeparser'; // docx & pptx import 'pdf-parse'; // pdf import 'd3-dsv'; // csv import 'mammoth'; // docx ... ```
`npx supabase@latest functions deploy process-document --use-api --debug` ``` Using access token for profile: supabase Loading project ref from file: supabase/.temp/project-ref Supabase CLI Using profile: supabase (supabase.co) Using access token for profile: supabase 2026/05/20 14:28:06 HTTP POST: https://api.supabase.com/v1/projects/apyynixhthznnlhrprsn/functions/deploy?slug=process-document Uploading asset (process-document): supabase/functions/process-document/deno.json Uploading asset (process-document): supabase/functions/process-document/index.ts Uploading asset (process-document): supabase/functions/process-document/types.ts Uploading asset (process-document): supabase/functions/_shared/gemini.ts Uploading asset (process-document): supabase/functions/_shared/types.ts Uploading asset (process-document): supabase/functions/_shared/edge.ts Uploading asset (process-document): supabase/functions/_shared/atlassian.ts github.com/supabase/cli/pkg@v1.0.0/function/deploy.go:127 (0xc00112) github.com/supabase/cli/pkg@v1.0.0/function/deploy.go:50 (0xbfefe8) github.com/supabase/cli/internal/functions/deploy/deploy.go:64 (0x166b17f) github.com/supabase/cli/cmd/functions.go:84 (0x2cdc7c9) github.com/spf13/cobra@v1.10.2/command.go:1015 (0x61b8c2) github.com/spf13/cobra@v1.10.2/command.go:1148 (0x61c205) github.com/supabase/cli/cmd/root.go:173 (0x2ce8f26) github.com/supabase/cli/main.go:11 (0x2cee08f) internal/runtime/atomic/types.go:194 (0x44953d) runtime/asm_amd64.s:1693 (0x485ce1) unexpected deploy status 500: {"message":"Function deploy failed due to an internal error"} ```
Cool, I didn't know about that. But what if you wanted to set a default `Access-Control-Allow-Origin`?
Yes, I meant 3 clients. But you may be right, I can't really think of a practical use case myself.
Personally, I'd love an option to add custom hooks to `withSupabase` to add more things to `SupabaseContext`. For example, for every edge function request I need to retrieve a user access token for a third party client. I'd love to add this client to the context.
A good addition to `SupabaseContext` would be `data`! Which depending on the request method would be a POST body or GET params, returned as a data object.
I had hoped we wouldn't have to pass CORS headers to every withSupabase call. Perhaps a good idea is for this and perhaps future global configuration to be done in a `server.config.ts` (or maybe the existing `config.toml`)?
Perhaps a nice addition would be a custom error handler you can configure, which can catch all thrown errors or failed responses. With this you could set up things like alerts, extra logs, etc.
It took me a while to figure out what `authMode` meant. Maybe renaming it to `allowed` would be less confusing?
I get having both a user-authenticated and admin supabase client is the most common, but what if you want a "guest" mode client, only using the anon key? I feel like that may be missing from the SupabaseContext.
Having both config.toml's `verify_jwt` and this feels a bit confusing/redundant. Any way to merge these into one solid API?
Supabase should integrate invalid/unused index indentification directly in their dashboard!
Do you still have the database password? With it you pretty much have whole database access, which would allow you to dump the entire database.
Check size zero rows = A Insert 1 row Check size with 1 row = B Estimated number of rows = C Total = C * (B - A) + A
if you're willing, come help test: https://github.com/coollabsio/coolify/pull/8316
none
https://github.com/supabase/cli/issues/4142#issuecomment-3869917978
Are these claims true?
You reckon its easier to setup with coolify or directly with hostinger?
Still using hostinger? How is it going? What do you need coolify for? Doesn't hostinger support supabase out of the box? Was it easy to setup? Were there any hidden costs?
My free pro credits end next month and I wont be able to afford their pricing. This could be good.