Skip to content
This repository was archived by the owner on Aug 9, 2024. It is now read-only.

[Feature Request] Using supabase backendless to directly call database for calls instead of your server #90

Closed
FoxTale-Labs opened this issue Aug 7, 2024 · 9 comments

Comments

@FoxTale-Labs
Copy link

FoxTale-Labs commented Aug 7, 2024

Related to issue -> #88
Adding to that I also want to migrate this to use supabase so the performance will be significantly improved and your server won't die no more. This will allow your server to chill a little as post creation, liking, disliking, and replies, etc. would go directly to supabase instead of an in-between.
This requires supabase rules to be setup though to prevent abuse, but is a fair trade considering it'll significantly help with the sites performance.

@FoxTale-Labs
Copy link
Author

I could implement this if you please while doing #88 after #20 has been implemented.

@FoxTale-Labs
Copy link
Author

FoxTale-Labs commented Aug 7, 2024

Adding: Things like the IQ test would likely still have to be passed through to the server for validation, and small things like image uploads (if you're not using supabase buckets, idk, didn't check yet). But we'd need to migrate to Supabase authentication, which won't be too hard honestly. Migrating to supabase authentication also gives the ability to get rid of discord login as then you won't need an SMTP server as supabase will send the verification emails out by themselves on their end for free.

Migrating to supabase authentication will be as easy as a little script or when entering the page you're prompted to go through a migration process of sorts, whatever suits you the best. We can talk about this on Discord if you please.
Discord handle: @Codingfox

@GStudiosX2
Copy link
Contributor

Related to issue -> #88
Adding to that I also want to migrate this to use supabase so the performance will be significantly improved and your server won't die no more. This will allow your server to chill a little as post creation, liking, disliking, and replies, etc. would go directly to supabase instead of an in-between.
This requires supabase rules to be setup though to prevent abuse, but is a fair trade considering it'll significantly help with the sites performance.

They already migrated away from supabase I think so I don't see why they'd want to go back to it

@FoxTale-Labs
Copy link
Author

Related to issue -> #88
Adding to that I also want to migrate this to use supabase so the performance will be significantly improved and your server won't die no more. This will allow your server to chill a little as post creation, liking, disliking, and replies, etc. would go directly to supabase instead of an in-between.
This requires supabase rules to be setup though to prevent abuse, but is a fair trade considering it'll significantly help with the sites performance.

They already migrated away from supabase I think so I don't see why they'd want to go back to it

oh damn i didnt know

@FoxTale-Labs
Copy link
Author

FoxTale-Labs commented Aug 7, 2024

well that sucks cuz the performance is significantly slow cuz its bottled by the server being, well, really slow.
we could also use firebase :trollface: (just kidding)

(just like now where it's AGAIN on an all time slow where supabase if the server went down in the backend it may not be entirely as bad as supabase would still make it mostly functional)

@FoxTale-Labs
Copy link
Author

package json still had references to supabase so i assumed he didnt migrate

@ghost
Copy link

ghost commented Aug 8, 2024

It was a problem with indexing, not the fact that we self hosted postgres. Also supabase was asking 25 dollars for a 2 core machine which is very overpriced and it couldn't handle the traffic.

@FoxTale-Labs
Copy link
Author

darn

@FoxTale-Labs
Copy link
Author

ok then

@FoxTale-Labs FoxTale-Labs closed this as not planned Won't fix, can't repro, duplicate, stale Aug 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants