Hi Bolke, Thanks for the comments, yes we do the same currently. We install system wide and run the app. as local user. The main problem I am having in this model is that when I install the app. system wide, the python modules are having dependency with system libraries and I don’t want to upgrade/downgrade the system libraries because a python module might not like the version of system library we have on the system. I am lookin for ways to workaround this.
Regards, Kalyan. On Jan 26, 2018, at 1:41 AM, Bolke de Bruin <[email protected]<mailto:[email protected]>> wrote: Installation under a different user works fine in a virtualenv. You can also install system wide and run as normal user (that is how we run it currently). Bolke Verstuurd vanaf mijn iPad Op 25 jan. 2018 om 23:21 heeft Pullagura, Kalyan <[email protected]<mailto:[email protected]>> het volgende geschreven: Hi Did you guys ever figure out the following or your suggestions would be much appreciated. 1. Installing Airflow application without ‘root’ user. If using root user, not to use system libraries for all the required python modules instead redirecting to a different location. 2. Installing Airflow using a local user or having an Airflow package itself with all the installation and all I have to run is a rpm or some install file. The above should help us to get faster when installing workers across our environment. Regards, Kalyan.
