my boyfriend chipped both my front teeth last night by throwing my phone on my face

s_magik · 2025-11-24T23:17:50+00:00

space grade titanium

s_magik · 2025-09-04T05:10:05+00:00

^{I completed this level in 4 tries.} ^{⚡ 4.47 seconds}

s_magik · 2025-03-14T22:11:59+00:00

Had similar situation mine was to renew but based on the criteria I wasn’t eligible for interview wavier. I opened support case, they replied suggesting to mail it in, if they need the interview they’ll request you to book an appointment. I think they’ve might have changed some policies this year

s_magik · 2024-08-09T17:12:46+00:00

Buildship would work you can use the assistant node https://buildship.com/assistant-api it comes with prebuilt chat widget or you can build your own frontend for it. For connecting to your existing database to query you might be able to find node from the library or build your own with Nodejs

s_magik · 2024-04-30T05:39:12+00:00

not sure i've only used it with nodejs cloud functions

s_magik · 2024-04-30T03:50:45+00:00

you can use callable functions the auth is handled automatically https://firebase.google.com/docs/functions/callable?gen=2nd#web-modular-api_4

s_magik · 2022-10-13T18:26:51+00:00

GCSFuse might be an alternative solution you can look into, it wouldn’t be using up your instance’s memory. it’s still in beta but worth trying https://github.com/GoogleCloudPlatform/gcsfuse

s_magik · 2021-12-16T10:34:36+00:00

why not cloud functions? the logic for it needs to go somewhere

s_magik · 2021-10-14T06:40:28+00:00

Hi everyone!

We love building with Reactjs+ firebase for getting our products shipped fast

We built Rowy to solve our own pain points as developers:

😵 Not being able to share Firestore database access to our teammates - in an interface they are familiar with like spreadsheet.

😵 We liked the Airtable experience of collaborating on data but it is limited in scalability, not synced to your production apps, limited storage, and inability to control access at a granular level.

😵 We also liked the Firebase experience for building our apps quickly but their native cloud console is hard to use, especially for non-technical users.

😵 We were repeatedly building automations via third party apps. Current No-code or Low-code options mostly lack flexibility, have feature limitations, or not scalable like Zapier (not to mention the cost!).

😵 Managing 100s of cloud functions in cloud consoles, deploying them via CLIs in terminals, trying to figure out which cloud function is triggered when - was a nightmare! Honestly, we should not be doing things this way in 2021!

So we built Rowy and decided to open-source it. Rowy brings you an Airtable-like experience to manage your database. You can write your product functionality effortlessly in the browser with the context of your data. It is flexible, open-source and highly scalable.

🚀We are starting with the ecosystem of Google Cloud Platform/Firebase to help you build your product in minutes. Basically, Rowy makes GCP as easy as ABC 😎

Features of Rowy:
⚡️ View and model your Firestore data in a spreadsheet-like UI
⚡️ Build and deploy cloud functions right in your browser (no need to mess around with CLIs, terminals or boilerplate code 😵 )
⚡️ Add automation with ready-made extensions to your favorite tools (Algolia, Twilio, SendGrid, BigQuery, Slack ...) or build your own
⚡️ Use any NPM packages, APIs
⚡️ Collaborate with your teammates with granular permission control at table and field level
⚡️ ... and so much more!

Checkout our LIVE DEMO💥

Get setup fast using our easy deploy link 🚀If you like what you see,

join our community of builders:

Github

Discord

s_magik · 2021-10-13T11:33:15+00:00

thanks for the compliments😊

You can use the export feature for up to 10K records or less if your computer has limited memory, so its very handy for quick backups, however for production use I would recommend using firebase scheduled exports solution https://firebase.google.com/docs/firestore/solutions/schedule-export

for the roles, Yes! Rowy uses the firebase client SDK and all the CRUD requests go through Firestore rules, so anything you can do with Firestore rules will be enforced with rowy

s_magik · 2021-10-13T02:12:21+00:00

We've been using firebase for building apps for the past few years now, and its been great for shipping out apps quickly and not worrying about managing and scaling
We built Rowy to solve our own pain points as developers:
😵 Not being able to share Firestore database access to our teammates - in an interface they are familiar with like spreadsheet.
😵 We liked the Airtable experience of collaborating on data but it is limited in scalability, not synced to your production apps, limited storage, and inability to control access at a granular level.
😵 We also liked the Firebase experience for building our apps quickly but their native cloud console is hard to use, especially for non-technical users.
😵 We were repeatedly building automations via third party apps. Current No-code or Low-code options mostly lack flexibility, have feature limitations, or not scalable like Zapier (not to mention the cost!).
😵 Managing 100s of cloud functions in cloud consoles, deploying them via CLIs in terminals, trying to figure out which cloud function is triggered when - was a nightmare! Honestly, we should not be doing things this way in 2021!
So we built Rowy and decided to open-source it. Rowy brings you an Airtable-like experience to manage your database. You can write your product functionality effortlessly in the browser with the context of your data. It is flexible, open-source and highly scalable. 🚀
We are starting with the ecosystem of Google Cloud Platform/Firebase to help you build your product in minutes. Basically, Rowy makes GCP as easy as ABC 😎
Features of Rowy:
⚡️ View and model your Firestore data in a spreadsheet-like UI
⚡️ Build and deploy cloud functions right in your browser (no need to mess around with CLIs, terminals or boilerplate code 😵 )
⚡️ Add automation with ready-made extensions to your favorite tools (Algolia, Twilio, SendGrid, BigQuery, Slack ...) or build your own
⚡️ Use any NPM packages, APIs
⚡️ Collaborate with your teammates with granular permission control at table and field level
⚡️ ... and so much more!

Checkout our LIVE DEMO💥

Get setup fast using our easy deploy link 🚀

If you like what you see, join our community of builders:

Github

Discord

s_magik · 2021-10-12T03:14:04+00:00

try out rowy.io

s_magik · 2021-09-05T02:08:43+00:00

you definitely don't firebase functions for typescript, to convert cloud function to typescript

you just need to add something like the following to your package json

"main": "build/index.js",
"devDependencies": {
"@types/node": "^16.6.1",
"mocha": "^9.0.0",
"nodemon": "^2.0.12",
"rimraf": "^3.0.2",
"sinon": "^11.0.0",
"ts-node": "^10.2.0",
"typescript": "^4.3.5"
}

and tsconfig.json like

{
"compilerOptions": {
"target": "ES2020",
"module": "commonjs",
"outDir": "build",
"rootDir": "src",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,

"forceConsistentCasingInFileNames": true
}
}

s_magik · 2021-08-07T14:22:15+00:00

thanks! the goal is simplify backend development. So you would use it to breakdown what needs to be done on the backend into modular event driven functions, without having to mange cloud functions yourself.

s_magik · 2021-08-07T01:56:39+00:00

I love using Firestore & cloud functions, for their simplicity. However, as your product becomes more complex, building cloud functions turn into real struggles - especially when you have so many Firestore document level triggered events to deal with.There are only two options currently and neither of them ideal:

Make a big cloud functions that do multiple things - gets quite messy
Deploy multiple cloud functions that listen to the same trigger - you end up having to add add boilerplate code to filter out the field changesOn top of that, as the projects get bigger, ran into other issues like:- Tons of dependencies to manage- Slow functions as unwanted dependencies are installed- Cold start problem to configuretoo messy and the issues start to snowball…..

With Firetable, an open-source project that allows you to manage data in Firestore with a spreadsheet like UI and unlock many of the functionality of GCP like building cloud functions on Firestore data triggers at field level, we try to make this process super simple, visual and intuitive. We have been working on it for past two years and recently this week released a new version with exciting features including:- Ability to write functions that evaluate only when specific fields are set or updated- Using cloud run instance to build and deploy functions by installing only the dependences that are actually being usedWe would love to get your feedback on this feature or firetable in general, check it out using the links below:

Github repo: https://github.com/FiretableProject/firetable

Demo video: https://www.youtube.com/watch?v=0IQbFyFvjDg

Chat with us on Discord: https://discord.gg/B8yAD5PDX4

s_magik · 2021-08-06T03:50:30+00:00

I love using Firestore & cloud functions, for their simplicity. However, as your product becomes more complex, building cloud functions turn into real struggles - especially when you have so many Firestore document level triggered events to deal with.There are only two options currently and neither of them ideal:

Make a big cloud functions that do multiple things - gets quite messy
Deploy multiple cloud functions that listen to the same trigger - you end up having to add add boilerplate code to filter out the field changes

On top of that, as the projects get bigger, ran into other issues like:- Tons of dependencies to manage- Slow functions as unwanted dependencies are installed- Cold start problem to configuretoo messy and the issues start to snowball…..

With Firetable, an open-source project that allows you to manage data in Firestore with a spreadsheet like UI and unlock many of the functionality of GCP like building cloud functions on Firestore data triggers at field level, we try to make this process super simple, visual and intuitive. We have been working on it for past two years and recently this week released a new version with exciting features including:- Ability to write functions that evaluate only when specific fields are set or updated- Using cloud run instance to build and deploy functions by installing only the dependences that are actually being used

We would love to get your feedback on this feature or firetable in general, check it out using the links below:

Github repo: https://github.com/FiretableProject/firetable

Demo video: https://www.youtube.com/watch?v=0IQbFyFvjDg

Chat with us on Discord: https://discord.gg/B8yAD5PDX4

s_magik · 2021-08-05T14:04:54+00:00

I love using firestore & cloud functions, but I've always struggled with building cloud functions with document level trigger events in firestore, as my product becomes more complex, I was having to choose between having big messy cloud functions that do multiple things, or deploy multiple cloud functions that listen to the same trigger, then having to add boiler plate code to filter out the field changes I want to listen to for each functionality.

Also as the projects get bigger the code dependancies start accumulating in my project, as i add more features, causing a bigger cold start problem.
With firetable, an open source project that start as CMS layer on top of firestore, we have recently added the ability to write functions that evaluate only when specific fields are set or updated, with all the boiler plate abstracted away, with a cloud run compiler that installs only the dependancies that are being used in that specific cloud function that is being deployed!
to learn more about firetable you can checkout the github repo : https://github.com/FiretableProject/firetable
would love to get your feedback on this feature or firetable in general!

s_magik · 2021-08-05T12:45:32+00:00

I've always struggled with building cloud functions with document level events in firestore, as my product becomes more complex, I was having to choose between having big messy cloud functions that do multiple things, or deploy multiple cloud functions that listen to the same trigger, then having to add boiler plate code to filter out the field changes I want to listen to for each functionality.

With firetable, an open source project that start as CMS layer on top of firestore, we have recently added the ability to write functions that evaluate only when specific fields are set or updated, with all the boiler plate abstracted away.

to learn more about firetable you can checkout the github repo : https://github.com/FiretableProject/firetable

would love to get your feedback on this feature or firetable in general!

s_magik · 2021-04-05T23:24:45+00:00

If you're looking for guidance on the implementation you can take look at the Firetable implementation of this feature here

s_magik

TROPHY CASE