some kind of storage about sveltelab HOT 9 CLOSED

wanna place the idea again to use git(hub) repos but not sure how much hassle that would be

The only issue I have with that is that the user will have to keep a GitHub repo for every REPL and that seems a bit much. We could store every REPL in a single GitHub repo managed by us but I feel like we would hit some limit.

I also thought about storing as plaintext on pastebin or GitHub gist, the filesystem is just a plain old JavaScript object right?

Absolutely, you can store it as POJO. Again the only problem I have with this is that I feel like we would very likely hit some sort of limit "at scale" and I fear that later on we would need to refactor this.

With the right abstraction maybe we could start with something that simple and level up before the end of the hackathon if we have time

from sveltelab.

I would love to store everything in an url but I think it's almost impossible because there are just too many files to do it.

What we could try is store as long as possible and if we go over the 2048 chars of the url we can store.

Where to store I hear you say? I'd say we can use supabase so that if we want to eventually also add login we can use their auth

from sveltelab.

wanna place the idea again to use git(hub) repos but not sure how much hassle that would be

I also thought about storing as plaintext on pastebin or GitHub gist, the filesystem is just a plain old JavaScript object right?

from sveltelab.

The only issue I have with that is that the user will have to keep a GitHub repo for every REPL and that seems a bit much. We could store every REPL in a single GitHub repo managed by us but I feel like we would hit some limit.

We could also have each user create one repo to store multiple projects as pojos 😄

from sveltelab.

Status on this right now: local storage

But since it's just POJOs we could have multiple "adapters", like GitHub, Pastebin, etc?

from sveltelab.

Status on this right now: local storage

But since it's just POJOs we could have multiple "adapters", like GitHub, Pastebin, etc?

I mean we could but do we need to have different options? For the hosted version we need only one...if we want we can abstract this away so that if someone want to deploy their own they could easily write an adapter.

from sveltelab.

nah we dont need different options, especially not for MHP, it was just an idea 😄

we will need definitely need sharable link for MHP tho

from sveltelab.

So the plan is pocket base with flyio right? Are we also using Pocketbase for auth the?
I'm down with that i guess. flyio has scaling options right? We can split the bill if you want 😁

from sveltelab.

So the plan is pocket base with flyio right? Are we also using Pocketbase for auth the? I'm down with that i guess. flyio has scaling options right? We can split the bill if you want 😁

Yeah I think this might be an idea, and yes we should be able to use poket base for the auth too...fly.io should handle scaling automatically and we should be able to run on the free tier.

I think it's time that we tackle this task...I'll give it a shot later (or on Monday)

from sveltelab.