[00:00:00] <imdeni>	 Let me try this ...
[00:01:41] <imdeni>	 The hidden directory `.heroku` is not in `/app`
[00:09:27] <bd808>	 imdeni: oh! I know. Run `launcher which python` and it should tell you the magic place
[00:10:11] <imdeni>	 Uhh. Me likes. Let me have a look ...
[00:10:16] <bd808>	 and really just doing `launcher python ...` as your command should keep you from ever caring where the venv really lives
[00:11:30] <bd808>	 `launcher` is a binary that should be in /cnb/lifecycle/launcher. It is the magic entry point that know how to run things inside any buildpack managed container
[00:14:41] <imdeni>	 Wooohoooooo!
[00:14:45] <imdeni>	 That's so easy.
[00:14:57] <imdeni>	 Thank you 🎉
[00:15:23] <bd808>	 glad we figured it out. Somebody show write something on a wiki somewhere about it ;)
[00:15:30] <bd808>	 *should write
[00:16:07] <imdeni>	 Or we can start a secret club only for the initiated /s :p
[00:17:16] <imdeni>	 I'll put it in my notes and when all is done maybe sit down and write-up various stuff that I have learned.
[00:32:59] <bd808>	 imdeni: I stubbed something at <https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Can_I_get_an_interactive_shell_inside_my_container?>. Please do add things as you figure them out. :)
[04:07:08] <imdeni>	 bd808: I did not see your message until now. I've bookmarked the page and will keep it in mind :)