🏳️🌈🍭 ↣ Web3 components with off-chain database integration #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…apping for moralis loops in [#6] + [HDASH-5 HDASH-4]
…ing on this in signal-k/theclub repo
📨💼 ↣ Auth working for [HDASH-5 HDASH-4 #6 STA-13]
🩸🧀 ↣ Adding more login styling (not quite finished yet) STA-13 STA-1
…-format 📊🍄 ↣ Anvil embed (iframe) merge. Bringing it into magic. | STA-15 STA-2
Currently, we're receiving build errors relating to the older pure supabase auth pages/components. We're not yet at the stage where we can test out the metamask signin, so I'm committing changes here and switching back to `supa-id` branch to see if the same build errors occur without these Moralis addons, the project builds correctly
Good news -> auth works now with the Moralis next/node package. I'll update the route/link for signin & user later. Next stop -> Magic.link!
Nexstep : get Magic talking to Supabase, Moralis!! Seems to be building fine...
…auth-to-supabase 🍀☠️ ↣ STA-16 : Add Magic authentication from Moralis-side to main auth
… handle user auth (parse)
…revising structure
…React + supabase for [#13]
The old dashboard design served its purpose. It got us to start planning where we are going to take things and some of the styling will be reused. However, right now I'm focusing on functionality so I've made the Account page front & center. The dashboard pages are still there, although I'd recommend going into https://github.com/Signal-K/sytizen/tree/sta-1-basic-dashboard-index-format + the issues derived from STA-1 on Linear to see the complete list of original dashboard components
…tend component for connecting to APIs (including with Py) for #1 Two new directories: `./Ansible` ↣ Contract & build files here. Will be moved into a new folder in the root React/Next.js project, but for now I'm leaving this in a separate node project to keep things separated for easier debugging `./client` ↣ Frontend client for interacting with the smart contracts in `Ansible` directory. Similar story to the directory positioning in `Ansible`. We'll migrate it over to the Node project in the root directory before merging this branch, however we will also transition as much as possible out of typescript.
…e Supabase configuration
Gizmotronn
added
duplicate
Gizmotronn
commented
Nov 24, 2022
There was a problem hiding this comment.
Make sure to keep an eye on this repo/branch as of commit 8faa46d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#18 ↣ Getting some of our test protocols in the frontend
#1 ↣ API calls to the Deepnote.com server through Flask (see #16, #12 & b0971a0, 03854d5)
#6 ↣ NFTs being displayed in frontend
#16 ↣ Authentication being handled
After this, we're going to go back to merging this into
sta-25-create-test-protocolssmart-contract-forbranch and then continue the linear method for PRs through the Linear issues as seen previously. Right now, though, we've got a next.js app that is talking to all the main pointers and we know what we need to do to get to the next step.Let's talk about using something like Filecoin to bridge the gap between off-chain & on-chain storage, as well as creating a more casual kanban very slightly integrated with Discord/Github.