You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an effort to reduce the amount of churn/scripting, explore the potential to create a symlink from brewpi/data to www/data and keep everything in the web directories owned by brewpi:www-data.
The logic to write to brewpi/data and then copy to www/data has been part of brewpi.py since v0.1 and there's a warning in the source code indicating that it's done to prevent locking the file:
# Do not write directly to www dir to prevent blocking www file.
I've posted a question for Elco to see if he remembers why that was done since it's hard to imagine locking the file to the point where reading it while it's being written would break things.
In an effort to reduce the amount of churn/scripting, explore the potential to create a symlink from brewpi/data to www/data and keep everything in the web directories owned by brewpi:www-data.
The logic to write to brewpi/data and then copy to www/data has been part of brewpi.py since v0.1 and there's a warning in the source code indicating that it's done to prevent locking the file:
I've posted a question for Elco to see if he remembers why that was done since it's hard to imagine locking the file to the point where reading it while it's being written would break things.
Only going to do his or #47 ... not both.
The text was updated successfully, but these errors were encountered: