this post was submitted on 10 Apr 2026
11 points (92.3% liked)

Programming

26464 readers
224 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
11
How do you handle automatic deployment for websites? (swg-empire.de)
submitted 1 day ago by bjoern_tantau@swg-empire.de to c/programming@programming.dev
6 comments fedilink hide all child comments
 

I have a small website with the git code hosted on my own Forgejo instance. I want to give my wife easy access to the code to update texts. I think using Forgejo is an easy enough interface for her to do that.

But how do I ensure that every commit is reflected on the website in a timely manner? I think webhooks are the usual answer. But do I add them to the website itself or do I run a separate service for that? If the latter, can you recommend one?

Or is there a better way? Seems kind of roundabout since the website and Forgejo run on the same hardware.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 1 points 1 day ago* (last edited 1 day ago)

Git push to Forgejo -> automated build, package, and deploy pipeline -> use secured credentials to upload via scp or ssh or sftp

Alternatives to copy-upload or upload-package and then extract via command is stuff like rsync (reduce redundant, unchanged file uploads) or a simple receiver service (for example REST endpoint that receives a package with an identifier key and secret key, that it extracts to a configured target folder).

What solutions are simplest or easiest depend on the target environment, and how much of it you control. If you host the website on Forgejo itself it's as simple as pushing the static files into the corresponding pages branch.