search

Andergraw / supabase-auth-ui-plasmic

Plasmic integration with Supabase and Auth UI template
GNU General Public License v3.0
3 stars 1 forks source link

Link to Project Not Available #1

Closed its-a-lisa closed 5 months ago

its-a-lisa commented 5 months ago

When clicking to see the link in the repo, the project didn't open.

Potential Solutions: Did you host the project somewhere and then add that link back into the configuration?

image

Andergraw commented 5 months ago

Since it's a project with custom code, you need to download and set the Github repo first to port 3000 in order to run the plasmic one.

its-a-lisa commented 5 months ago

Ok, it might make sense to make that clear in the ReadMe

It currently states "I have also created a demo project in Plasmic" with a link that takes you to the project, so the assumption would with what is written there, that you'd be able to go directly to the project.

The original Supabse Demo also has custom code components, but the link in the ReadMe to the Plasmic Project takes you to the Project and it is visible without doing the extra steps of downloading the code and configuring the project to localhost because they've hosted the project to plasmic-supabase-demo-git-master-plasmic.vercel.app/plasmic-host so that when someone goes to the projec they custom code components are available.

The plasmic documentation has the recommendation on how to manage the code components and app hosts.

Andergraw commented 5 months ago

First of all, I appreciate your effort in making this repo more complete :). I'm editing the readme to make your point more clear.

Nevertheless, if you have already played with the Plasmic ecosystem, their example is different, since the components they are using are Plasmic components being substituted with custom code (I am talking about the Github project referenced here, not the Supabase one you are linking). This is an imported whole custom component that NEEDS to be app hosted in order to be available in the Plasmic Studio editor. It's a different scenario. Sorry, but deploying this example to Vercel is beyond the scope of the repo. Maybe in the future I update it.

On the other hand, as stated in the readme, this is not an example made to cover the whole process of starting with Plasmic, but goes directly into making this component work with Plasmic Auth integration.