build: set API keys

[rndquu]

This PR sets params for ubiquity bot prod instance:

1. supabase API endpoint
2. supabase public anon key (which is safe to use on the client side because we've enabled RLS for all of the tables)

[ubiquibot]

• 2894e92

[gitcoindev]

Hi @rndquu I have just checked on my fork (the other opened PR) and I see an empty table, is the 'Realtime on' option set in supabase? The previous key works fine for me.

[rndquu]

Hi @rndquu I have just checked on my fork (the other opened PR) and I see an empty table, is the 'Realtime on' option set in supabase? The previous key works fine for me.

I don't know where are those keys from but they are certainly not from the bot's prod supabase instance

is the 'Realtime on' option set in supabase?

yes

We have RLS enabled for the logs table but don't have a policy to allow public read access from the logs table so the logging app frontend won't display any logs until we add a new policy for the logs table

[gitcoindev]

Hi @rndquu I have just checked on my fork (the other opened PR) and I see an empty table, is the 'Realtime on' option set in supabase? The previous key works fine for me.

I don't know where are those keys from but they are certainly not from the bot's prod supabase instance

is the 'Realtime on' option set in supabase?

yes

We have RLS enabled for the logs table but don't have a policy to allow public read access from the logs table so the logging app frontend won't display any logs until we add a new policy for the logs table

All good then, thank you for the quick reply. I can approve from my side.

[0x4007]

We have RLS enabled for the logs table but don't have a policy to allow public read access from the logs table so the logging app frontend won't display any logs until we add a new policy for the logs table

I think this needs to be included in the migration file or done again manually for the new database instance from the refactor?

[rndquu]

We have RLS enabled for the logs table but don't have a policy to allow public read access from the logs table so the logging app frontend won't display any logs until we add a new policy for the logs table

I think this needs to be included in the migration file or done again manually for the new database instance from the refactor?

There is already a PR with the migration ubiquity/ubiquibot#864

[ubiquibot]

Available commands

- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why. 
  example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address. 
  ex1: /wallet 0x0000000000000000000000000000000000000000
  ex2: /wallet vitalik.eth

@rndquu