Thanks for your suggestions Michael, The fact is that Capistrano wasn't designed with this case in mind. There are easy workarounds by overriding the shell, and making sure that the host is capable of sourcing specific files, or uploading files as part of an early step before changing the shell, but because the underlying host system is designed to be customizable in this regard, Capistrano, by design leaves those configuration parameters to the host machines.
I strongly second the suggestion to think about using containers, on platforms where they work, they are infinitely better than Capistrano and as the maintainer for over 10 years now I can say that containers (or, any technology giving you control over your environment *absolutely*) are an incredible productivity, security and predictability win. Regards, Lee Hambley http://lee.hambley.name/ +49 (0) 170 298 5667 On Mon, 6 May 2019 at 22:57, Michael Richardson <[email protected]> wrote: > > I did some hacks to attempt to get different settings per-server, for the > case where I was deploying an app multiple times for different tenants on > the same host system. I wanted to change the user, deploy_to, and > annoyingly, I had to have a different git_wrapper_path, because otherwise > they get deployed to /tmp, and conflict with each other. > Many would suggest this is an ideal use case for containers, and maybe > I'll back and do that, but at the time containers were just too immature on > the target platforms I cared about. > I'm not clear if you are trying to do something similar or not. > > While I eventually got it working well enough for my needs, I what I found > is that the places where certain variables were set/initialised or > defaulted made it rather difficult. I think that I have a pull request > lingering if you really want it. > > My suggestion is to attempt to localise the things you need to do, and > then create a task that runs config/deploy/${HOSTNAME} to do the things you > need to do which are server specific. > > -- > You received this message because you are subscribed to the Google Groups > "Capistrano" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/capistrano/fcc1ddef-6f38-47a0-aa72-2e583d258a99%40googlegroups.com > <https://groups.google.com/d/msgid/capistrano/fcc1ddef-6f38-47a0-aa72-2e583d258a99%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLVN8_Qwsw9fUNg6MQtAirbHWod2%3D6YAY_nkQV-T_ycqiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
