timharek-no-becx2e.txt (3751B)
1 [1]Skip to content[2] 2 Tim Hårek 3 4 • [3]Blog 5 • [4]About 6 • [5]More… 7 8 1. [6]Index 9 2. [7]Blog 10 3. [8]Switching to SourceHut Builds 11 12 [9][10](Photo)[11][email protected][12]PGP key 13 14 Switching to SourceHut Builds 15 16 Published December 8, 2022 17 Last updated June 18, 2023 18 2 minutes read 19 20 Earlier this year in a post, [13]What should you choose for deploying your 21 static websites?, I wrote about what CI/CD[^1] you should chose for your static 22 websites. And I concluded on using just using git-hooks. Well, by the title of 23 this post you've probably guessed that I'm indeed changing my mind. 24 25 After using this workflow for a while for a few projects I've realized a few 26 things. 27 28 1. I miss having proper version control for the testing, building and 29 deploying steps. 30 2. It requires more effort to setup. 31 3. I need to manually configure notifications for when something goes wrong. 32 33 There are probably more things, but these are the ones that have bothered me 34 the most. For step #2 I made a shell-script, [14]git-hooks, so that I don't 35 have to remember every intricate detail each the time. 36 37 So why [15]SourceHut? [16]Last time I wrote about this topic I found out their 38 tool is the easiest to configure and use in my opinion. They have support for 39 hosting of static sites, and you also have access to a bunch of packages for 40 the [17]different images they provide. Ben Busby's blogpost, [18]GitHub vs 41 GitLab vs SourceHut, also helped me switch to SourceHut. A key difference 42 between my git-hooks workflow vs SourceHut builds is speed, my git-hooks 43 workflow took a few seconds, but with SourceHut it takes up to 1 minute. But 44 I'm in no rush. 45 46 As of writing I've moved my personal website over to SourceHut's build-system, 47 and I've moved the website for the place I live ([19]my post about it) to it as 48 well. This project didn't even use git-hooks, it used GitHub Actions. My plan 49 is to move [20]Everyday Privacy over, which is using Vercel today. I also want 50 to start adding more tests and checks to my other small projects, so that I can 51 get notified if something doesn't pass after I've pushed to remote. 52 53 I'm looking forward to using SourceHut more, I like how simple it is. It takes 54 away a lot of unnecessary bits that other source-forges has. 55 56 [^1]: Short for: Continuous Integration / Continuous Deployment 57 58 Tagged with 59 60 • [21]#cicd 61 • [22]#devops 62 • [23]#git 63 • [24]#sourcehut 64 65 363 words 66 67 [25]Reply via email 68 Last deploy: 2024-10-23 69 70 • [26]Stats 71 • [27]Privacy 72 • [28]Connect 73 • [29]Subscribe 74 75 76 References: 77 78 [1] https://timharek.no/blog/switching-to-sourcehut-builds#main 79 [2] https://timharek.no/ 80 [3] https://timharek.no/blog 81 [4] https://timharek.no/about 82 [5] https://timharek.no/more 83 [6] https://timharek.no/ 84 [7] https://timharek.no/blog 85 [8] https://timharek.no/blog/switching-to-sourcehut-builds 86 [9] https://timharek.no/ 87 [10] https://timharek.no/.well-known/avatar?size=250&quality=90 88 [11] mailto:[email protected] 89 [12] https://timharek.no/public-key.asc 90 [13] https://timharek.no/blog/what-should-you-choose-for-deployment 91 [14] https://github.com/timharek/git-hooks 92 [15] https://sourcehut.org/ 93 [16] https://timharek.no/blog/what-should-you-choose-for-deployment 94 [17] https://man.sr.ht/builds.sr.ht/compatibility.md 95 [18] https://benbusby.com/gh-vs-gl-vs-sh/ 96 [19] https://timharek.no/blog/i-made-a-website-for-the-place-i-live/index 97 [20] https://everyday-privacy.com/ 98 [21] https://timharek.no/tags/cicd 99 [22] https://timharek.no/tags/devops 100 [23] https://timharek.no/tags/git 101 [24] https://timharek.no/tags/sourcehut 102 [25] mailto:[email protected]?subject=RE:%20Switching%20to%20SourceHut%20Builds 103 [26] https://timharek.no/stats 104 [27] https://timharek.no/privacy 105 [28] https://timharek.no/connect 106 [29] https://timharek.no/subscribe