As I mentioned before in an earlier part, there was a specific tool that was on my self-hosted runner that plays an important role in this next few steps. That being Tailscale. I’m not going to go into great detail about what Tailscale is but, just know, it allows me to talk to all my devices inside my Tailnet without exposing anything externally. Very nifty to have and makes connecting/hosting things really easy. ...
This is a continuation of the last part in the Pipelines Series. Now that I had my self-hosted runner ready to go and assigned to take workflows, I was ready to start with making my first pipeline. Github is really good about providing necessary steps and files that are needed for certain task and this is no different. After i went into actions, I was able to pick a .yaml template. I went ahead with the basic Simple Workflow yaml. ...
As discussed in my first post, I initially wanted to lay out a plan for a pipeline in Github that would automagically push changes to a development environment as I coded. The first problem with this is: developers (myself included) are trigger happy. They love to push changes because I mean why not. The second problem I had was that I wanted the app to run continuously. Keeping these two things in mind, I hopped over to Github and started learning about pipelines. Now I have messed a bit with Gitlab pipelines so I had a general idea of what to expect. ...