danames
commented
2 years ago Just for clarification, these would be essentially one-time settings that the admin would specify when first using the app store. After that any use of the app store would use these stored parameters for the sake of ease later on... yes?
Daniel P. Ames, Ph.D., P.E. Professor, Civil & Environmental Engineering,Brigham Young University, Provo, Utah, USA Past-President, International Environmental Modelling & Software Society Editor-in-Chief, Environmental Modelling & Software http://ceen.et.byu.edu/content/dan-ames https://ceen.byu.edu/directory/dan-p-ames http://www.researchgate.net/profile/Daniel_Ames http://scholar.google.com/citations?user=S0GUCeUAAAAJ
On Thu, Oct 14, 2021 at 9:10 AM Nathan Swain @.***> wrote:
@rfun https://github.com/rfun @msouff https://github.com/msouff @rileyhales https://github.com/rileyhales I've been tasked by Dr. Nelson to create virtual machine images on the major cloud providers that contain a production installation of a Tethys Portal. I'd like to include the Tethys App Store in the image to make it easier to install apps. However, there are a few constraints that I need to work with, so I have a few questions/suggestions about the Tethys App Store that would make it easier to use in these images:
- How does the Tethys App Store restart a production instance of Tethys? Is the supervisorctl command hard-coded? Can the restart command be specified? I have created a systemd unit file to manage Daphne/Tethys, so supervisortctl can't be used to restart it. Instead systemctl needs to be used.
- I know the app stores the root password currently, can you specify the username of the root user i.e. can it use sudo with a user with sudo permissions? When I created the Azure image, it deletes the root account, but I think it is recreated when the VM is provisioned. I can get around this constraint by having the user set the root password, but it would be nice if I could just have it configured to use the tethys user that I've created in the image.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BYU-Hydroinformatics/tethysapp-tethys_app_store/issues/18, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2PZ5CV654DHRA36BUJJWDUG3XHRANCNFSM5F743IRQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
swainn
@rfun @msouff @rileyhales I've been tasked by Dr. Nelson to create virtual machine images on the major cloud providers that contain a production installation of a Tethys Portal. I'd like to include the Tethys App Store in the image to make it easier to install apps. However, there are a few constraints that I need to work with, so I have a few questions/suggestions about the Tethys App Store that would make it easier to use in these images:
supervisorctlcommand hard-coded? Can the restart command be specified? I have created a systemd unit file to manage Daphne/Tethys, sosupervisortctlcan't be used to restart it. Insteadsystemctlneeds to be used.sudowith a user withsudopermissions? When I created the Azure image, it deletes the root account, but I think it is recreated when the VM is provisioned. I can get around this constraint by having the user set the root password, but it would be nice if I could just have it configured to use thetethysuser that I've created in the image.