Deploying multiple versions of the same app to distinct users on same server: passenger config

Jerome

3/27/24, 7:00 AM

Context: Creating multiple users on a single server, each of which will have its copy of an application and own database. To be server by nginx

configuration /etc/nginx/conf.d/mod-http-passenger.conf requires that the default set-up be modified so that it points to the deploying user

### Begin automatically installed Phusion Passenger config snippet ###
passenger_root /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini;
# passenger_ruby /usr/bin/passenger_free_ruby;
passenger_ruby /home/deploying_user/.rbenv/shims/ruby;

But this file is a server wide configuration belonging to root, thus shared between users. The attempts to date have the same versions of rbenv, ruby & the application installing and running for each user - which should be the normal production environment.

So the passenger pointers & shims are apparently OK; preliminary tests do not indicate any issues. Still, this is not an ideal situation.

How can mod-http-passenger.conf be modified to allow pointing to each deployed user?

0 + 0

nginx

phusion-passenger

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Deploying multiple versions of the same app to distinct users on same server: passenger config

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.