fix: use url module

[mtfoley]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Description

README update and different require for endpoint config. Just reflects what I needed to do in order to get this running locally.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[github-actions]

Congrats on making your first Pull Request and thanks for taking the time to improve Open Sauced! ❤️! 🎉🍕
Say hello by joining the conversation in our Discord

[mtfoley]

@0-vortex I've been doing some other poking around and found that if I seed locally from what's in the open-sauced/actions/hot-supabase directory, I have to drop the repos/users foreign key constraint.

Also, when I do supabase db reset and the seed.sql file gets used, the data doesn't make it into the tables and I wonder if something similar is going on.

[0-vortex]

@0-vortex I've been doing some other poking around and found that if I seed locally from what's in the open-sauced/actions/hot-supabase directory, I have to drop the repos/users foreign key constraint.

Also, when I do supabase db reset and the seed.sql file gets used, the data doesn't make it into the tables and I wonder if something similar is going on.

are you running supabase locally? otherwise you are juggling between adjusting the dev or the prod db, both things which shouldn't do right now as the entire structure should sit in the backend rather than actions.

To figure out if the seeds are broken just run them manually in supabase ui 😁

[mtfoley]

Yeah, I'm running it locally. i saw the docker containers pull and spin up, and i saw the supabase/seed.sql file get used. however, in the studio, the tables are empty. i realize now, the shell script to download copies of the SQL files from the actions repo was unnecessary, but i still wonder if we should troubleshoot why that initial seed file didn't fill up the db locally.

[0-vortex]

Yeah, I'm running it locally. i saw the docker containers pull and spin up, and i saw the supabase/seed.sql file get used. however, in the studio, the tables are empty. i realize now, the shell script to download copies of the SQL files from the actions repo was unnecessary, but i still wonder if we should troubleshoot why that initial seed file didn't fill up the db locally.

Sorry for the late reply - the seed file is being executed via psql inside the docker containers, similarly to what we are doing in the seed.sh script, hence the errors are not visible unless you check the process logs after you sh into the containers.
You can check the error yourself simply by renaming seed.sql and running it locally as described above, however the most likely culprit is bad insert order, conflicting with relationships, running the individual seed files in the logical order would fix this (i normally seed it this way and then adjust script in actions, however we are partially divergent until backend is deployed fully)

[0-vortex]

We are moving off of this system for seeding, will close this :D