Conversation

Notices

1. Embed this notice
   Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 15-Dec-2024 03:56:20 JST Jan Wildeboer 😷:krulorange:

   #Lazyweb. Has anyone built a #Forgejo Action to run #Jekyll and put the generated files in a directory on a web server? I know about all the GitHub automation using their GitHub pages, but I want to #selfhost and already have the sources of my blog in a git repo on my local forgejo instance. Ideally a solution that runs completely locally, without downloading tons of stuff from docker repos :)

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Sunday, 15-Dec-2024 04:00:30 JST Beowulf

     in reply to

     @jwildeboer I do it with zola, so this could be pretty much the same?

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 15-Dec-2024 04:31:01 JST Jan Wildeboer 😷:krulorange:

     in reply to

     I am truly impressed. Within minutes I got files, advice and support from everywhere around the #fediverse. I now have no more excuses and will have to work hard to get it all up and running and report on teh HOWTO in an upcoming blog post which might already be after I moved my blog to my own server. The Fediverse is full of geeks that are happy to share. And that's not a bad thing in clickbait times! Thank you all :)

     Evan Prodromou repeated this.
   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 15-Dec-2024 04:36:21 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • Elena Rossini ⁂

     @_elena If you need more stories on how the #fediverse brings people together to build new solutions that change the world bit by bit, without Venture Capital, the Open Source Way, here is one. Happy to discuss at FOSDEM in the social web dev room :)

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Sunday, 15-Dec-2024 04:39:55 JST Evan Prodromou

     in reply to

     • Elena Rossini ⁂

     @jwildeboer @_elena It's the place to be!

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Sunday, 15-Dec-2024 05:15:27 JST Beowulf

     in reply to

     • Piotr Siuszko

     @MevLyshkin Ok, published it. You can find it at one of these places:
     - https://codeberg.org/Beowulf/Snippets/src/branch/main/Actions/zola-build-deploy.yaml#
     - https://paste.sr.ht/~beowulf/54849d6d432ef8963080fb2f62f4509ca25f8384
     @jwildeboer

   • Embed this notice
     Piotr Siuszko (mevlyshkin@mastodon.gamedev.place)'s status on Sunday, 15-Dec-2024 05:15:28 JST Piotr Siuszko

     in reply to

     • Beowulf

     @Beowulf @jwildeboer ping

     Jan Wildeboer 😷:krulorange: repeated this.
   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Sunday, 15-Dec-2024 05:15:29 JST Beowulf

     @jwildeboer Sure, I'm currently thinking of the best way to share it (it's on my private git server) 😆

     *File was sent privately. If someone is also interested, pls ping me.

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Monday, 16-Dec-2024 06:02:55 JST Jan Wildeboer 😷:krulorange:

     in reply to

     So after reading through the replies and doing some more research (and a LOT of mistakes), I guess I have a basic action working that

     - clones the repo
     - runs Jekyll
     - lists the generated files

     On my own #Forgejo instance and using my own forgejo-runner that runs rootless with #podman.

     That's a good start! Thank you all for giving me input :)

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Monday, 16-Dec-2024 06:19:14 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • A feral Natalie

     A HUGE thank you to @some_natalie who has built a secure and rather lightweight Jekyll build container that runs rootless without throwing errors! Read her detailed blog entry on that at https://some-natalie.dev/blog/jekyll-in-a-can/ :)

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Monday, 16-Dec-2024 06:42:13 JST Beowulf

     in reply to

     @jwildeboer I'm interested on why you did configured got this way. Are you committing something later in the workflow?

     And interesting that you need safe directory, I saw this was set by the checkout action but wasn't necessary for me.

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Monday, 16-Dec-2024 06:56:27 JST Beowulf

     @jwildeboer Like I did it also in the action I send to you.
     And I didn't need to set the safe directory manually. :D

     And regarding if you want to commit something: This was related to the lines where you set the user mail, name and initial branch - if you just clone this isn't needed? 🤔

   • Embed this notice
     Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Monday, 16-Dec-2024 19:06:44 JST Jan Wildeboer 😷:krulorange:

     in reply to

     • Beowulf

     After long hours of trial and error, and a bit of sleep I have arrived at this for now. An almost universal action that takes a repo with Jekyll sources, builds the static site and commits the static files it to another repo called "web" in a folder with the site name. That repo can be automatically cloned to the web server to update the site! (that final part is what I will work on today). Thanks to @Beowulf for sharing some inspiring sed lines :)

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Monday, 16-Dec-2024 19:23:55 JST Beowulf

     in reply to

     @jwildeboer Interesting approach with two repos.

   • Embed this notice
     Beowulf (beowulf@fosstodon.org)'s status on Monday, 16-Dec-2024 19:33:25 JST Beowulf

     @jwildeboer I understand this. My way was that the CI pushes via rsync to the server.

     This makes more sense for me, because the site has a lot of binary files (mostly images), so I don't want to have another big repo which just consumes resources.

     But your approach is also interesting. With your way, the CI doesn't need access to the server.