Joel's Open Source Dev Blog

Note: posted a little late but I wanted to wrap up the OSD700 conclusion So we've finished the Winter 2022 semester and did I set myself up for a tough one. I have to admit it was underestimated my ability to keep up and a lot of things were piled up on top of school, it was a little hectic to say the least. Nevertheless, I still want to wrap up, and conclude my OSD700 journey. Release 3.0.1 .... and .2, .3, and so on and so forth. Safe to say we haven't 100% "successfully" shipped the release. But it's up and running okay on production.... at least it looks like it. Our Supabase migration didn't quite turn out as well as hoped, so we've got a major bug on prod right now and our feeds won't update with new posts.  Tue really deserved credit for doing majority of the debugging and releasing, Duke also has been trying to come up with fixes for whatever's going wrong in prod. But right now I think everyone is trying to catch a break, the semester'

First, sorry for the lack of updates. I know I'm missing a lot of details from the previous Telescope post. But to sum it up, lots of new features and fixes were shipped throughout 2.8 and 2.9 but since 3.0 alpha which was released 2 weeks ago, we've had to shift our priorities towards the mainline features that were to be shipped in the 3.0 major release which we're shipping this week. Supabase Progress So we've finally got our own Supabase client running on staging, and we're planning to deploy it to production for 3.0 So that's really exciting.  Jerry has been lending a hand by coming up with more tables we can use for more info (i.e. github_data) Not only that but he's written a script to backup our Supabase/Postgres data in the events of a failure, that's really neat! This process involves starting a temporary container for the purpose of running the backup script. We've been migrating things like accounts and feeds to the Supabase tables. But w

Fragments is a cloud-based microservice made with AWS services. This was our main assignments throughout the semester for CCP555 (which Dave also teaches) Gradually implementing Amazon web services to a basic web app made with nodeJS.  Fragments is a web app made to store and distribute small text and image files for a rhetorical company that require the fragments microservice to support their new system. As for it's architecture, it's pretty simple. At its core, its an express app, built to serve as an HTTP REST API for all the fragment operations. I'll try and detail the Amazon web Services used to support the app. Amazon Cognito So for authorization (which I've learned in this course is the most 'necessarily' complex topic to learn) we used Amazon's Cognito service. Cognito is so great for simplifying a lot of the authorization process instead of having to build it yourself from the ground up. In addition to the authentication that it provides, it stores