2.9 Planning : Supabase, and Auth Stuff

-

This week, we're heading into the planning phase of 2.9, which I am sheriff-ing again with my fellow coursemate Roxanne (Yes, I completely forgot to talk about 2.8, I'm sorry!) and Telescope is increasingly becoming a different app as we reach 3.0 in a 4 weeks. Though I've landed a couple PRs and had a hand in shaping up the Supabase, I still feel like I haven't contributed enough. Well these last 2 releases are going to be vital and Dave's really emphasised on it. We need to start taking ownerships of our specific areas and specialties so that we can be more productive in these last 2 releases. So here are my plans for 2.9

Supabase

Obviously should come to no surprise. I've been working with Duke and Dave for the past releases, and it's really been shaping up. This release we want to get the wheels rolling for Supabase and finally utilize it in Telescope production. So here's what's on the menu

Docker Secrets

First of all, we need to figure out a method to store our secrets (not limited to the supabase stuff) on production, since the secret used to sign the JWTs for supabase should be confidential and not be accessible by the public. Fortunately, Dave has already outlined the solution on how we can do this using Docker secrets, and it goes something like this

1. Create the new secret on production/staging boxes like

            printf "abcd" | docker secret create github_token -

2. You can view these secrets using docker secret ls or docker secret rm <name>
3. these secrets will be mounted to a read-only temporary fs in our containers at

    /run/secrets/<secret_name>

4. set up the secret in a container using docker-compose like this.
5. Figure out how to turn the secret files to env variables

Dave has always helped getting the ball rolling as it can get really confusing for some of us on how we can approach these problems. So I'm hoping I can help execute this and get it pushed for the next release.

Sign-On

Now that auth is handled by Supabase, and Duc finished the sign on flow, we can finally implement our sign in feature. It's been sitting in our code, commented out this whole time, and production will finally be able to make their own accounts and sign in. This will make use of our feeds tables as well.

Supabase DB

With the new supabase db, we're also starting to migrate our feeds into the table created by Duke in our supabase db. As well as store user info. During our 2.9 discussion this past Tuesday, Jerry also had an idea to store Github user data for future use, which I thought was a great idea. Supabase is so versatile and we spent a lot of work implementing it into Telescope, so utilizing it even more to add new features and use its full potential sounds like a great way to go about it.

Summary

It's a little hard splitting half your time being a sheriff and contributing towards the next release. But I'm enjoying both right now and just hope I can dedicate my time to doing productive work in both roles. I'm still itching to push my big work I can show off, and it's what Dave is trying to push all of us to achieve. 

"My goal is that you'll all have some work that ships that you can be proud of as you move into your career"

        

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more