šŸŸ„ [FREE] Redis Connector

Extensions
, ,
1

redislabs

Redis Connector

This extension works in conjunction with a Webdis front end, a Redis instance on an Ubuntu server. It provides a fully featured redis experience. It offers two levels of password security and three levels of in-database separation. If you have not used Redis before, there is a lot of reading to do, and some not insignificant setting up to do as well.

Hopefully this is all explained on my web site:

Redis <> AI2

.

  • Latest Version: 1.0
  • Tested: This has been tested, to exhaustion, on App Inventor 2 using Android 10 and 12 devices, companion 2.62, and compiled apk. It may work on other derivatives....e.g. Kodular/Niotron/etc.
  • Released: 22 March 2022
  • Last Updated: 22 March 2022
  • Built: Using the Rush Extension Builder by @shreyash

Credits
My thanks to @oseamiya and @ewpatton for their help with some of the trickier bits of code.

Extensions (these will not just work, you will need to setup a server, redis and webdis):

Redis Connector v1

Redis Connector Expert v1 (a sort of barebones, for the initiated)

Enjoy :smiley: , and all feedback and comments welcome.

Available for use in any MIT AppInventor projects or competitions

#####################################################################
This work by TIMAI2 is licensed under a
Creative Commons Attribution-ShareAlike 4.0 Unported License with attribution.
Please use name = TIMAI2 and link to this source page when giving credit.
#####################################################################

11 Likes
2
  • 526 days since the first post
  • 11 likes (One is mine)
  • 0 Replys

Honestly, you must feel like me, when my mom likes one of my photos on Instagram. :face_exhaling:

In order to fulfill what I have been entrusted with, this week I dedicated myself to think of a project to develop with Supabase and Appinventor.

The issue is that it is necessary to cover several things about Postgre, SQL, Android and Appinvetor. So that all this together creates a good, beautiful, cheap, true and robust App or system (why not?).

  • One of that issues is the real-time messaging system regarding changes in the BDD, and notifications.

As you can't use the real-time notification system, if it's not through Fireba$e (which inadvertently puts you in debt to your teeth).

Supabase suport realtime, via Webhook, Http, EdgeFunctions and obviously... all via Fireba$e.

But reading your post, documentation on your page and Itoo usage...

  • Is there a way I can hit the cloudDB API, with an HTTP POST from supabase?

Let me explain the flow:

1- I configure my cloudDB in appinventor with its tags (AK: channels, users and broadcast groups) EX: user, firefighters, civil defense, coast guard, lost animals, municipality, morality police, etc.
2- Each tag has a value of 0 or 1 (0 = no notifications and 1 = has notifications).
3- For each change in the database (in any of these broadcast channels), a POST request is sent from Supabase over HTTP, with {Tag:Value}. = {user:1}
4- Rise a notification saying "You have a notification in the tag"
5- The user clicks on the notification and automatically opens the application and displays the message with the information to be displayed.

  • That's basically the rough, crude, and cheap idea, then you add colors and rounded edges.

The thing is that from Appinventor, I only have the ProjectID, RedisPort, RedisServer and Token.

I won't lie, a couple of hours ago i internalized a little more about Redis, so I'm in diapers.

But I would like to know how possible it is to do that flow with cloudDB and the data that we have from it.

And I don't have the computing resources to throw a linux server and try.

My PC

chingolita
chingolita1600Ɨ1200 124 KB

spec
spec1200Ɨ1600 139 KB

5 Cats of power consumption (sometimes more)

5cpc
5cpc1600Ɨ1200 108 KB

3

I will give a short and simple answer...

We have to move beyond the bounds of the cloudDB component.

If you use Webdis to access a Redis server, then you are sending http requests. Therefore if Supabase can send http requests to Webdis, this will access the data on the redis server and return the required output.

It is then a case of handling the return data for notifications/AI2 app.

There is also this thing:

1 Like
4

:thinking: hmmm...

I see...