diff --git a/src/content/posts/software/designing-this-website.mdx b/src/content/posts/software/designing-this-website.mdx index 7f54624..1b378c2 100644 --- a/src/content/posts/software/designing-this-website.mdx +++ b/src/content/posts/software/designing-this-website.mdx @@ -3,7 +3,7 @@ title: "designing this website" date: "18/06/2024" --- -## Update: Port to Astro (22/05/2025) +# Update: Port to Astro (22/05/2025) I'm expanding my website to included more detailed algorithms, implementations, write-ups, and low-level optimization case studies. @@ -29,7 +29,7 @@ On the upside, I have around the same LOC, a dead-simple blog post setup ([here] The choice of Astro was of no significance. It did the job and that's all that matters. I'm not quite a fan of the funky `---` syntax to separate HTML and JS, though. I find it counterintuitive to separate the UI and the frontend logic, which ought to be tightly coupled. I don't want to imagine working on larger files in Astro. -## HTML, JavaScript, and CSS +# HTML, JavaScript, and CSS That's all there is to it. @@ -42,7 +42,7 @@ I thought about using the following frameworks: But I did not actually _need_ any of them to make this site look decent. -## What I've Learned +# What I've Learned Of course, most people build simple websites like these to learn a new technology or framework, not to use an optimal tool. That's actually why I [hosted this website on AWS](/posts/software/from-github-pages-to-aws.html). diff --git a/src/content/posts/software/from-github-pages-to-aws.mdx b/src/content/posts/software/from-github-pages-to-aws.mdx index 008d819..1c899fd 100644 --- a/src/content/posts/software/from-github-pages-to-aws.mdx +++ b/src/content/posts/software/from-github-pages-to-aws.mdx @@ -3,7 +3,7 @@ title: "from github pages to AWS" date: "15/06/2024" --- -## pages begone +# pages begone Though GitHub Pages may work for hosting your small, internal, static site, I don't think Pages is the right choice for _anyone_: @@ -11,7 +11,7 @@ Though GitHub Pages may work for hosting your small, internal, static site, I do 2. Limited SEO control: not a downside if you don't want want traffic... 3. Static & client-side only: keep your options open -## why aws? +# why aws? I used pages before because I had little knowledge of cloud computing. @@ -25,7 +25,7 @@ AWS is: 2. Secure: soon to be used by VISA, which holds security to a nearly stupid extent (seriously, I can't even clone a repository) 3. Well-documented: everything in the documentation worked _first try_. This is extremely rare in software, so compliments to Chef Bezos. -## the setup +# the setup This website is pure HTML, CSS, and JavaScript. @@ -46,7 +46,7 @@ A user request can be modelled as follows: ![system design of my portfolio website](/public/posts/from-github-pages-to-aws/website-design.webp) -## difficulties +# difficulties The hardest part of hosting this website was interfacing with GoDaddy. diff --git a/src/content/posts/software/hosting-a-git-server.mdx b/src/content/posts/software/hosting-a-git-server.mdx index 04c7775..a6a4f04 100644 --- a/src/content/posts/software/hosting-a-git-server.mdx +++ b/src/content/posts/software/hosting-a-git-server.mdx @@ -3,17 +3,17 @@ title: "hosting a git server" date: "07/05/2025" --- -## why +# why No reason. Perhaps to host personal files in the future. AWS's micro free tier is great, too. -## what +# what - Write my own git web ui - Support clones from my own website - Host private files on my git ui -## the process +# the process I detail self-hosting a git server on an AWS t2.micro instance ("free" for 1 year) as of May 2025. [Git's instructions](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) were vastly outdated so hopefully this saves a lucky reader some time. @@ -70,7 +70,7 @@ I detail self-hosting a git server on an AWS t2.micro instance ("free" for 1 yea 11. There are a variety of choices for web ui, including [cgit](https://git.zx2c4.com/cgit/), [gitweb](https://git-scm.com/docs/gitweb) (I do not recommend this—the scripts are ancient and require manual tuning), and some even heavier options that allow for further customization. I am not a fan of viewing code on the web, so you cannot in [my custom ui](https://git.barrettruth.com). I spin up a simple python server to walk the projects in `/srv/git` and configured a systemd service to run it in the ec2 box: -## lessons +# lessons - **It feels great to do things yourself**: I used GPT-4o for linux server command help, that was about it - **Always ask "what is this?" before using something**: this would've saved me hours of realizing a 12 year old perl script should not have been running my git ui. diff --git a/src/content/posts/software/my-cp-setup.mdx b/src/content/posts/software/my-cp-setup.mdx index c97b17a..ccb7465 100644 --- a/src/content/posts/software/my-cp-setup.mdx +++ b/src/content/posts/software/my-cp-setup.mdx @@ -5,7 +5,7 @@ date: "15/04/2025" Source code [here](https://github.com/barrett-ruth/dots/blob/main/nvim/lua/cp.lua). -## my goals +# my goals I wanted the following features in my competitive programming (cp) setup: @@ -13,7 +13,7 @@ I wanted the following features in my competitive programming (cp) setup: - Speed: instantaneous, non-blocking running/debugging; automatic environment configuration and easy code testing - Editor-Agnostic: while I do provide first-in-class NeoVim integration for my setup, it should be easily portable to _any_ os/editor -## the solution +# the solution Some (POSIX-compliant, of course) scripts and a `makefile` are more than enough. I created the following intuitive way to interact with my CP setup: @@ -24,7 +24,7 @@ Some (POSIX-compliant, of course) scripts and a `makefile` are more than enough. That's it. The `makefile` relies on some scripts that compile code and run the corresponding executables. -## neovim integration +# neovim integration ![screenshot of my neovim competitive programming setup](/public/posts/my-cp-setup/cp-setup.webp)