blues-stack VS starchart

Now, if you followed the PR link, you would have seen that it was merged but had a failing check. And that is what was addressed later while adding Playwright. Since the project was setup using the Remix blues stack, it shipped with cypress for end-to-end testing. The cypress folder had some tests but these were not modified when the app was setup since we intended to use Playwright. This resulted in the typecheck job failing, since it was also checking the cypress folder: tsc && tsc cypress

This week, after some discussion, a plan was made for release 0.1 of starchart. This involved getting an initial app setup using Remix's blues stack so that people could code on top of it. Next step involved creating some issues which could be addressed in release 0.1 release 0.2 and some for further releases. As I am mostly focused on front-end and testing, I created the following issues:

The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.

Blues Stack: Remix Stack for deploying to Fly with PostgreSQL, authentication, testing, linting, formatting

I think this might fit https://github.com/remix-run/blues-stack

Remix doesn’t just give you a bunch of tools and ask you to go build your thing, they lead by example which is why they have the concept of Stacks. Stacks are essentially templates/starter kits that gives you the groundwork for a complete project right out of the box. For our project, we will use the Blues Stack which gives us a fully configured Remix project with Prisma, Tailwind and an entire module that shows how to use those tools to build a CRUD feature. I mean honestly, I feel like I shouldn’t even be writing this post since the template did all the work already. Oh well… I’m in too deep now so might as well finish it.

As per issue 105 and PR 174, we have a docker container that will act as a local IDP with a few users it recognizes that it will return SAML response claims for.

The past week, I worked on setting up basic user dashboard pages and routes for starchart. These routes involved pages for management, creation, and help for domains and certificates. The ideas was to setup a basic template, such as a heading, and the routes so these could be easily updated once the designs were finished.

I worked on domains table and created a PR with that, which is currently in review.

This week, my main focus is to work on seeding the database for Starchart project. (see PR) I thought it would be more complicated, but it's actually just writing query with Prisma to insert rows of data into database tables, and there's a bit of script setup.

My first task with porting over middleware used by Satellite and adding it to Remix's server. Remix's Blues Stack, by default, uses Morgan, but we wanted to use Pino instead. However, Pino seems to cause a problem, so David has to switch to using Winston.

Login and Logout Changing User Model after Prisma Schema change

Main work

The past week I worked on setting up Playwright, and Chakra UI with starchart. Chakra UI is needed so that their components could be used to build the web pages, and Playwright is to be used for end-to-end testing.

The one PR I created this week was initialisation of Chakra UI theme. For now it only includes shades of our "brand" color, which is well-known Seneca's red color. This color is now applied as a default one for all UI components such as Button, Checkbox etc. After several iterations of code reviews and updates from my side the PR was merged.

This week, I focus on creating an initial schema for the project through using Prisma. This is for a MySQL database, and the PR for the initial schema is here.