satellite VS workspace-images

This week we released Telescope 2.8 and, as part of the new release, we moved the Satellite project inside of the Telescope monorepo. Satellite is the microservice framework used by Telescope.

The issue was caused by a recent PR that changed SECRET to JWT_SECRET (To use with the latest version of Satellite) without adding the required variables in env.staging and env.production.

There is an ongoing issue that I am trying to address: moving the Satellite repo inside Telescope to complete the monorepo. I haven't been successful so far, so I will ask other students to collaborate on this one, and maybe it can be done by Release 2.7.

The second thing I'd like to note is the last bit of my quote, where I will probably laugh. I can look back now and definitely laugh. Not only did I do my first release, I did my second and third. Being sheriff was overwhelming, I wanted to encourage all our contributors and push them in the right direction, ask if they required support when issues went stale, but also handle new high priority issues.

A lot happened this week, on Tuesday meeting the sheriff, went through the task to-do for release 2.6, and on Thursday it was a triage of Pull requests and issues. During the triage, I go assigned to more issues, in the area of react native, docker, and a bit of front-end fix. Also, did my first release on an open sources project in Satellite repo.

For release 2.6 I have been working on some issues already especially in satellite repo. Issues:

I opened a PR to solve this issue. I removed most of the file src/backend/lib/redis.js and some packages to fully utilize Redis connection from Satellite. After some back and forth, it got merged but a bit later Duke found out that it broke master, the backend couldn't start.

Continuing on from that blog, I ended up creating two more pull requests as I was wrapping up 0.4: #22

To start, I thought I could solve Telescopes Issue by fixing some code on Telescope or Satellite in order for the CORS errors to stop. I soon learned that the main problem wasn't fixable from our code bases and had to be fixed from Terminus.

This week, I worked on porting our ElasticSearch client to Satellite. That one was more of a pain in the ass than I thought it would be, mainly because it wasn't starting. Also, intellisense wasn't as strong as it was with Redis, so I had to turn to documentation alot, both for regular and the mock versions of ELS. You can find my PR for that, here.

This solution starts from the GitPod-provided MySQL image. That does not give everything you need for a functioning Drupal site, but it does meet the basics of a LAMP stack.

You might need to replicate some steps from https://github.com/gitpod-io/workspace-images/blob/main/base/Dockerfile inside your dockerfile.

It occurred because go install was run by root in the Dockerfile. So running sudo will solve it, but the image doesn't have the command. By the way, it won't occur in the official image because it sets the USER properly.

By default, Gitpod uses the gitpod/workspace-full image which includes a lot of tools which weren't needed for Telescope. Since Telescope only really requires Docker, Node and pnpm, creating a custom Dockerfile to have a smaller image for the gitpod workspace using gitpod/workspace-base would be much better than using the default one.

Both Gitpod and Github Codespaces have config files based on Docker that configures your whole env. On Gitpod their config system uses a .gitpod.yml file which stores your workspace config info and a .gitpod.Dockerfile file which sets up a docker image that you can use to run your workspace. By default, Gitpod uses a standard docker image as the foundation for workspaces, the standard image has most of the default tools and programs devs require, plus you can also build on top of it to add small additions to it.