blog-post-workflow VS ssh-agent

Now, we will create a new action for your repository. There is an awesome action template that can be used directly. This action will fetch the blogs from your Medium profile and put that on your GitHub profile page.

I would like to be able to add an RSS feed with latest posts to my github profile via https://github.com/gautamkrishnar/blog-post-workflow

Thanks to GitHub-flavored markdown, there's a lot you can do in your profile README. Mine has links to sites I've built, recordings of talks I've given, ways to connect, and a Blog Post Workflow written by @gautamkrishnar using Github Actions.

That space alloted labeled "Recent Updates" is meant to list scraped RSS or feed from any of my blogs. I used this Github Action.

Paste the code inside your yml file. Get the RSS feed URLs of your blog post sources and replace the feed list in the code above, indicated with an arrow. Visit this repository and scroll down to get the RSS feed URLs of some popular blogging platforms. Simply remove the links in the code above and paste yours in, separated by a comma if you have multiple sources. Don't remove the quotation marks.

The github action supports a readme_path parameter. After a quick dive in its source code I noticed that this file could be anything, not necessarily a markdown file. Problem solved!

As I planned to start blogging, I stumbled across this idea as I myself was looking to start a blogging presence of my own. As I looked around, I was able to only find one easy-to-use GitHub action that would allow me to add a list of my posts to my readme. Sadly, I was disappointed to discover that this action had little formatting, only setting up the posts as a bulleted list of links, which was less than appealing to the eye.

If you are active in writing blog posts, maybe you will want to add them to your readme profil page. Mine are not generated using some action because I have linked them to the repository concerned, but you can do it using blog-post-workflow (the description of how to use it are in the readme).

Once the image has been built and pushed, you only need to trigger the deployment using Kamal. We use the webfactory/ssh-agent to establish a connection to our production server. After installing the required Ruby dependencies, it’s only a matter of running Kamal. As the image is already built and pushed, we use the --skip-push flag.

When using Github Actions, to build projects I have been using the ssh-agent approach (https://github.com/webfactory/ssh-agent), with this means the Cargo.toml looks like this:

Thankfully when I reached out on Twitter, Jonathan Carter on the Codespaces team, seemed to suggest they may be working on a native SSH integration one day. Till then, here is the solution I came up with. This process address some sequencing issues around devcontainer.json's Lifecycle Scripts and when your Dotfiles are installed. Credit to VS Codes Using SSH Keys guide. Also, some things here are pulled directly from the GitHub Action to setup SSH. Again, thanks to Johnathan Carter for the ideas.