Bug #6994
closed
[Deployment] our rails packages need to install certain files/directories as owned by $WWW_OWER
Description
Bug¶
Right now those ownerships are ensured in the scripts
/usr/local/bin/arvados-api-server-upgrade.sh
/usr/local/bin/arvados-workbench-upgrade.shbut that is not good enough because they are not a postinst script yet; the files/directories get installed with incorrect ownership, nginx is started, and things go to hell because Passenger can't write into its tmp directory.
Fix¶
Convert these scripts into postinst scripts for their respective packages. This may require handling new arguments passed by the package system that describe the operation happening, and only triggering on relevant operations; and possibly having different scripts for different targets.
Updated by
Updated by Brett Smith over 8 years ago
How do you feel about making the upgrade script a proper postinst script as a way to fix this?
Doing it right in the package does seem a little nicer, but also trickier to do on Red Hat-based distributions. Red Hat sets up a user per HTTP daemon, so the proper owner depends on what daemon they're using (Nginx, Apache, …).
Updated by Brett Smith over 8 years ago
- Subject changed from [Packaging] our rails packages need to install certain files/directories as owned by $WWW_OWER to [Deployment] our rails packages need to install certain files/directories as owned by $WWW_OWER
- Category set to Deployment
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Brett Smith over 8 years ago
- Description updated (diff)
- Story points set to 2.0
Ward signed off on the idea.
Updated by Brett Smith over 8 years ago
- Target version changed from Arvados Future Sprints to Kanban
Updated by