Skip to main content

ยท 2 min read
Abhishek Gowda
warning

I am assuming this is a new machine setup or a machine which is occasionally used and does not contain any previous setup. And for most part I will be talking about Linux machine

Setting up SSH keyโ€‹

Adding SSH key in gitlabโ€‹

  1. Sign in to gitlab
  2. Click on your user profile. You should see a dropdown modal
  3. Click preference on it. You will be taken to the preference page of your profile
  4. Look for SSH keys on the left navigation. If left navigation is closed click on "Sidebar Navigation" button or press Ctrl+\. Navigation sidebar will open.
  5. You should now be in SSH keys page
  6. Locate Add new key button
  7. Click on it โ˜๏ธ (Add new key)
  8. In your machine

Navigate to user directory

cd ~

Locate .ssh directory, it is an hidden directory, navigate within it

cd ~/.ssh

Copy public key that is generated

cat <encrypted_file_name>.pub

copy the contents

  1. Past the copied key into key text area
  2. Pick a title so you could differentiate when and where the token is located
  3. Choose Usage type. I prefer to use the same token for Authenticating and signing, you could have different token setup
  4. Choose the duration of the key when it should be invalidated.

  • My suggestion/steps would get outdated, leaving gitlab ssh key reference link

ยท One min read
Abhishek Gowda

Backgroundโ€‹

I wanted a different packages to work on different things. I don't want to have a single package that would contain everything. I wanted flexibility on creating and testing code. So went to nx package based approach.

Prerequsiteโ€‹

I used nx VS code extension to create/generate the package. This made it easier to create the package.

Setupโ€‹

We just need to follow along the setup steps and the package would be created at the end of the steps.

nx follows it's own project configuration - https://nx.dev/reference/project-configuration

For more information the above ๐Ÿ‘† link can be followed.

Referencesโ€‹

ยท 3 min read
Abhishek Gowda

Backgroundโ€‹

This is a documentation repository for my advent of code solution.

Motive behind this website, I tend to forget things which I've done. And when the similar problem arise that needs to be solved, I try to look into git history to find how I solved it. But never I've gotten a thing out of git history. (Which is completly my mistake)

I've 2 repositories, one for the actual code and the other for hosting the documentation. The actual code is hosted in a private repo and this repo is a public compiled docusaurus site. I'll elobrate how I've set this up.

Setupโ€‹

Initilizing projectโ€‹

  1. With repo with nx
npx create-nx-workspace@latest <project_name> --preset=ts
  1. Update package.json to use pnpm
{
"name": "<project_name>",
"engine": {
"node": "^20",
"pnpm": ">=8"
}
}
  1. Change package-lock.json file into pnpm-lock.yaml file
pnpm import

Adding git submoduleโ€‹

  1. Move into the project
  2. Add submodule to the project, in this case we had already created a different empty repository for this.
git submodule add <repository_url>

With this there should be a new file called .gitmodules should be created. With the information about the module added.

At this point we can commit the progress.

Creating packages within the mono repoโ€‹

The root repo we have is a mono repo. Now we have to create a new file with name pnpm-workspace.yaml. Inside it added the folder structure. This is what I've

packages:
- 'src/*'
- 'documentation/*'

Creating docusaurus folderโ€‹

There is a generator for creating of docusaurus in nx. But I prefer using the create command from docusaurus.

npx create-docusaurus@latest documentation classic --typescript

With this the setup for the repository is completed.

Update docusaurus configโ€‹

There are couple of configuration changes that needs to be done in docusaurus.config file.

With this the setting up of documentation repo will be completed. But we still need to host this in github pages.

Hosting in github pagesโ€‹

The submodule repo we added is a public github pages repo

Enabling github pagesโ€‹

  1. Create a public repo.
  2. Go to repo setting.
  3. In the left section, there we will find Pages section.
  4. Scroll to Build and deployment section
  5. Select from Deploy from a branch
  6. Select Branch - main and folder - root
  7. Click on save.

It would take few seconds and the github page should be up.

There should be Visit site button. Click on it, will take to the deployed page. Copy the url of the page.

Go back to the Landing page of the repo.

In the right hand side there we will find a gear icon โš™, click on it. And enable Use your Github pages website check box.

Conclusionโ€‹

With this we should have things read for deployment.

Let tweak some script in the documentation package.json copy build script command and paste it and rename it to build-github-pages

Update the command as

"build-github-page": "docusaurus build && cp -rf build/* <sub_module_location>", // update submodule location here

Now run the command pnpm build-github-page.

With this the submodule will be update.

Add the update files in the root repository and commit with appropriate message.

  • Traverse to the submodule directory.
  • Add all the files to git and push the changes.
  • After few seconds the github page will be updated with the changes.

๐ŸŽ‰ We have successfully deployed docusaurus as github pages ๐Ÿš€