61 ms·

Caddy and self-hosting's cool and all, but I think I'd miss push to git to deploy and just not having to manage 'stuff'. Although, I did move a site from netlif

• cube2222 2y ago
  Yeah this, I too prefer hosting static websites via static storage or CDN, rather than having to operate anything. CloudFlare Pages is great, and so is GitHub Pages for developer websites.
  • mobilio 2y ago
    I also vouch for CF Pages! Killer features for $0. EXCEPT redirects of .html to / (slash) that you can't control.
• atwrk 2y ago
  If your content is static anyway, you can just rsync to deploy instead of push to deploy: rsync -e "ssh -p $(SSH_PORT)" -P -rvzc --cvs-exclude --delete $(LOCAL_CONTENT) $(SSH_USER)@$(SSH_HOST):$(REMOTE_DIR) Self-hosting then essentially just means doing apt install nginx once.
  • _joel 2y ago
    That would expose .git, unless other nginx config masked it. cvs-exclude is for cvs, right?
    • atwrk 2y ago
      It was for cvs, because rsync is old, but nowadays also filters out .git, .svn, .hg etc. In any case this is supposed to only sync the rendered content from $(LOCAL_CONTENT), not the templates used for rendering.
      • _joel 2y ago
        You think they'd change the name to vcs-exclude, then.
        • pepa65 2y ago
          Backwards compatibility.
          • _joel 2y ago
            Can retain that and add a vcs-exclude, right?
• always_imposter 2y ago
  You could setup a github action(if your repo is hosted on Github) or use something like gitea in your local environment to manage your repo and then you push changes to that gitea repo, it has an action runner like github's which does all the automating stuff for you. It is only one time setup pain point, after that you are all set.