30 ms·
I don't think most people would need multi-user permissions on a git repository for a personal blog, right? In my case, I just push to GitLab and have CI run to
by drakonka 5y ago
I don't think most people would need multi-user permissions on a git repository for a personal blog, right? In my case, I just push to GitLab and have CI run to deploy to S3 via a GitLab-specific IAM user key/secret set as a repo env variable.
- southerntofu 5y agoWhen i say multi-user i don't necessarily mean human users. Some bots could be pushing content like comments from 3rd party interfaces (email inbox, HN thread, HTTP form) and i wouldn't like them to have write access to content/ or themes/ folder, only to a dedicated folder. Also interesting to question the whole supply chain security. What is Gitlab gets hacked? Surely you could deploy from/to your own infra using Gitlab as a source of truth by verifying PGP signatures (like with guix git-authenticate), but then how to apply the aforementioned ACLs? If you have resources on that topic, i'm all ears.
- gitgud 5y ago> When i say multi-user i don't necessarily mean human users. Some bots could be pushing content like comments from 3rd party interfaces Could be easier to use either another repository or a 3rd party comment system like Disqus
- drakonka 5y agoI think this might be over-complicating it a bit for a personal blog. There are comment systems like Commento, Disqus, Hyvor, etc that let you just embed a JS snippet into your layout for comments (if one even wants to support blog comments at all). Regarding GitLab getting hacked, while it is of course a concern I'm not sure it's any more of a concern compared to using any other hosted blog service. You'd have to consider how secure any hosting solution is, whether it's Wordpress, GitLab/AWS, Medium, or anything else. As a benefit, GitLab (unlike many other blog hosting services) supports U2F MFA.