This commit is contained in:
nihilist 2024-10-22 21:37:02 +02:00
parent de5fa8754d
commit c044dd3fc8

View file

@ -76,7 +76,7 @@
<div class="col-lg-8 col-lg-offset-2"> <div class="col-lg-8 col-lg-offset-2">
<h2><b>What tools can i use ? </b></h2> <h2><b>What tools can i use ? </b></h2>
<p>Let's say you have a project with too many todolists for you to complete in one month like in our example from this <a href="../microworkflow/index.html">previous tutorial</a>. While this kind of todolist organisation may work for individual work, this may not be ideal for collaborative work, where let's say you have 10 people that want to work on your project.</p> <p>Let's say you have a project with too many todolists for you to complete in one month like in our example from this <a href="../microworkflow/index.html">previous tutorial</a>. While this kind of todolist organisation may work for individual work, this may not be ideal for collaborative work, where let's say you have 10 people that want to work on your project.</p>
<p>Rather than literally sending them your todo list text files over chat, you guessed it, you need a better, more serious solution. If you are familliar with Git (which is a distributed version control system, used to track versions of files), you may be thinking Github already, it is the biggest service for hosting open source code online, <a href="https://github.blog/news-insights/company-news/github-and-microsoft/">but the problem is that it was acquired by Microsoft in 2018.</a>, so if you're like me and you don't want your repositories taken down whenever microsoft feels like it (like what happened to <a href="https://www.eff.org/deeplinks/2023/04/update-tornado-cash?language=el">Tornadocash</a>), you need to put your repositories elsewhere:</p> <p>Rather than literally sending them your todo list text files over chat, you guessed it, you need a better, more serious solution. If you are familliar with Git (which is a distributed version control system, used to track versions of files), you may be thinking Github already, it is the biggest service for hosting open source code online, <a href="https://github.blog/news-insights/company-news/github-and-microsoft/">but the problem is that it was acquired by Microsoft in 2018.</a> So if you're like me and you don't want your repositories taken down whenever microsoft feels like it (like what happened to <a href="https://www.eff.org/deeplinks/2023/04/update-tornado-cash?language=el">Tornadocash</a>), you need to put your repositories elsewhere:</p>
<img src="2.png" class="imgRz"> <img src="2.png" class="imgRz">
<p>Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Gitea. We'll use our <a href="https://git.nowhere.moe/">Gitea instance</a> for this tutorial, but you can do the same on your own gitea instance.</p> <p>Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Gitea. We'll use our <a href="https://git.nowhere.moe/">Gitea instance</a> for this tutorial, but you can do the same on your own gitea instance.</p>