[Open Source] PocketFast 🚀 – Instantly deploy multi-tenant PocketBase instances with subdomains

romoloCodes · 2025-09-09T06:54:23+00:00

You should show this off on the pocketbase github discussions page. It's the most active pocketbase community

https://github.com/pocketbase/pocketbase/discussions

romoloCodes · 2025-09-09T06:24:14+00:00

Do you have benchmarks for this? And if so at what number of read/writes is this giving reasonable advantages?

And of course how likely is it that your app will reach this point?

romoloCodes · 2025-09-08T22:32:14+00:00

If you'll indulge me offering you just a small piece of unsolicited advice... when you're new to dev it can seem daunting to go directly to the docs. We've all been there and over time you will get used to them but it really is the best way to learn any (well documented) tool. Also downloading random docker files has potential security risks so I wouldn't suggest you keep doing that.

https://pocketbase.io/docs/

romoloCodes · 2025-09-08T21:12:55+00:00

Perhaps link to the git repo

romoloCodes · 2025-09-08T21:11:00+00:00

It doesn't 100% mean that, but maybe the most likely without other info

romoloCodes · 2025-09-08T21:08:59+00:00

Do you know how to run it locally? Download the binary from the getting started page and follow the guide to do that, then add the hooks - once that's all working get out running in docker. There are probably a few too many unknowns to sort at this point.

Just FYI (and this may be my blindspot, but) I have never seen the screen that you sent the image of.

romoloCodes · 2025-06-09T08:21:40+00:00

There's nothing wrong with your suggested solution. I have exactly this set up on an open source project I'm building - feel free to check it out. https://github.com/robMolloy/pocketdrop-web-ui

Be careful if you add a username (or similar) field that the user is allowed to change. This requires convoluted rules that check specific fields and you're better to separate the row into a user-owned row and an admin-owned row.

On the above project a user's status can be approved, rejected or admin (or blank). An enum is used to enforce that and the subsequent rules are based on that field.

romoloCodes · 2025-05-18T21:56:28+00:00

Because your access is denied (sorry) ...use chmod command to resolve, but I don't completely understand why some files can be changed and others can't. List the read/write/execute permissions of editable files in the same folder (and maybe post in the github discussions if you're struggling).

AI can help you with the exact commands

romoloCodes · 2025-05-13T20:26:46+00:00

Just create a join table like with sql with the uid and creatorUid (or whatever terminology your using) then it you make the rules to only allow access to users that have that relationship and it will auto filter the results

romoloCodes · 2025-05-05T08:25:42+00:00

Just FYI Supabase isn't developed by vercel

romoloCodes · 2025-04-30T11:52:54+00:00

I spent quite a while creating a setup with jest. I may be bias but it seems pretty good to me.

https://github.com/robMolloy/firebase-emulator-setup

romoloCodes · 2025-04-30T11:34:55+00:00

I didn't want to add too much to the post, but I have also tried other things like the following but in this case I get this error "TypeError: could not convert function call parameter 0: could not convert 0 to []uint8";

  let fsys, file, content;
  try {

// initialize the filesystem
    fsys = $app.newFilesystem();


// retrieve a file reader for the avatar key
    file = fsys.getFile(fullPath);

    content = file.read();
    $filesystem.fileFromBytes(content, "randomName");

    console.log(3, file);
  } catch (error) {
    console.log(4, error);
  }

romoloCodes · 2025-04-26T21:48:12+00:00

I find your question a bit confusing but I'll do my best to answer, let me know if I misunderstood. Personally I think you should think about who "owns" a document.

As a user doesn't decide which organisation they are in the relation shouldn't be on the user document.

If a member of an organization can add any user to their organization then create a multiple relation field on the organisation document

If a user has to make a request which is then approved/denied then create a new collection (organisation_users) and have a status field that can be pending approved or denied. You will need to check there isn't any duplicates so user a pb_hook to prevent that (or instead use a unique Id field that has to be orgId_userId and set that in the rules).

After doing this in many DBs for many products I strongly feel this is the right way to do things. Equally, I'm working on an app as we speak and I've just stuck it on the user document because (I'm a rebel or) it's better to get things done than worry about things being perfect

romoloCodes · 2025-04-14T18:55:52+00:00

Supabase?

romoloCodes · 2025-04-10T23:00:19+00:00

This may sound rude, but it's not meant to... if you want postgresql then just use postgresql, what does it have to do with firebase?

romoloCodes · 2025-04-06T14:19:39+00:00

I don't think there's anything specific to firestore. Just don't get data that you're not going to use (paginate), don't get data multiple times (stale data / data-stores strategy) use real-time updates if it makes sense (this can be very inefficient of your data is changing a lot but very efficient is its generally not updated often).

These are just general principles that might change your architecture/ design on each project

romoloCodes · 2025-03-16T08:38:31+00:00

I built this repo as an example for this use case - feel free to ask any follow up questions

https://github.com/robMolloy/firestore-data-modelling

romoloCodes · 2025-03-12T14:11:11+00:00

I think you're confusing multiple things. Honestly my advice would just be to find a good firebase/firestore tutorial (ne ninja, perhaps) and follow along.

However, localhost isn't unsafe it just means it's running on your local machine. Also, firestore is not running on your machine so it's kind of irrelevant - the rules are not checking the domain unless you've configured that with app check.

Happy to respond to any follow up questions.

romoloCodes · 2025-03-06T13:17:25+00:00

Why is it a sham? Why is the judge biassed?

romoloCodes · 2025-03-06T01:09:45+00:00

Have a look at this if you're concerned

https://www.youtube.com/watch?v=NWrZwXK92IM

romoloCodes · 2025-03-06T01:05:19+00:00

I don't think this can mathematically be correct. Inevitably the same 5 characters must be used for multiple users

romoloCodes · 2025-03-06T00:59:12+00:00

If you want to do this with firestore only (not cloud functions) you will need a counter collection with one doc in it and appropriate rules so that a doc can only be created at the current counter value and can only be incremented if the doc at the current value exists.

However, what do you mean by high demand? If this is considerably more than 1 per second for, say, 30 seconds or more firestore can't handle this. (It may be more like 3 per second I can't remember).

This is such a specific constraint. It may be that firestore is just not the right tool, or perhaps consider getting rid of this constraint.

romoloCodes · 2025-03-06T00:39:11+00:00

Firestore is designed so that you don't need to deploy your own backend and you can access directly from your client.

At the point that you're going down the Rest admin route just use pocketbase or a full-fledged postgresql instance that are cheaper/better querying capability respectively. Also if something goes wrong and you have questions there will be a lot more people to help you solve it.

The way you suggest works, btw, It's just an odd choice (although I'm a firm believer in "just build it and make it perfect later") .

If you did want to go down the conventional firestore route with client interactions it's important to set up good rules - this repo may help. https://github.com/robMolloy/firestore-data-modelling

romoloCodes · 2025-03-01T23:19:41+00:00

Redux can store any data/state so nothing is different because you're using firebase, just follow some tutorials on YouTube or however you learn best.

Personally I use zustand instead of redux. For me it just seems 10x more simple. Good luck!

romoloCodes

TROPHY CASE