.bssg_cache permissions issues with multiple authors #35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
TL;DR
I have implemented BSSG for a simple blog on our LAN to track our activities for home schooling. The kids each have to post at the end of the day. Unfortunately, we are experiencing some file permissions issues.
The setup
Debian 12 VM on my TrueNAS box (hostname codex.local):
We each have shell logins to codex.local and I recursively set the permissions for /var/www/html to belong to the users group with RWX. (The users group similarly owns the stuff in /opt/BSSG.)
Because bssg seems much happier to be run directly from the /opt/BSSG directory, I wrote a little script for them:
The problem
Everything works for me. Everything works for them--except the build. They keep getting a permissions error that they cannot write to the /var/www/html/.bssg_cache file, so they can't finish the build. When I look at permissions, that file is now owned by my user group:
I have tried to chgrp it back to users and
./bssg.sh buildruns without issues or errors for me. But when running./bssg.sh buildas user 'ian' there are further permissions issues. I've attached a transcript of the relevant part.This whole system is exceedingly clever, but unfortunately beyond my ability to make work with our current setup. As it stands, I just run the build myself whenever they tell me they're done; I could automate that, but it would be better if I could make it work the way it is supposed to.
Is there a smarter way to set this up for multiple users? I could simply create a user solely for managing the journal, but I was hoping to gradually expand the services on this box as they get more comfortable on the command line, and I am allergic to multi-user login accounts, even for something so trivial.
Thank you in advance for any ideas!