{"action":"created","issue":{"url":"https://api.github.com/repos/rstudio/shiny-server/issues/143","labels_url":"https://api.github.com/repos/rstudio/shiny-server/issues/143/labels{/name}","comments_url":"https://api.github.com/repos/rstudio/shiny-server/issues/143/comments","events_url":"https://api.github.com/repos/rstudio/shiny-server/issues/143/events","html_url":"https://github.com/rstudio/shiny-server/issues/143","id":102473920,"number":143,"title":"Shiny server not referencing project-specific lib path using packrat (except on Pro edition)","user":{"login":"jburos","id":923453,"avatar_url":"https://avatars.githubusercontent.com/u/923453?v=3","gravatar_id":"","url":"https://api.github.com/users/jburos","html_url":"https://github.com/jburos","followers_url":"https://api.github.com/users/jburos/followers","following_url":"https://api.github.com/users/jburos/following{/other_user}","gists_url":"https://api.github.com/users/jburos/gists{/gist_id}","starred_url":"https://api.github.com/users/jburos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jburos/subscriptions","organizations_url":"https://api.github.com/users/jburos/orgs","repos_url":"https://api.github.com/users/jburos/repos","events_url":"https://api.github.com/users/jburos/events{/privacy}","received_events_url":"https://api.github.com/users/jburos/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-08-21T22:33:37Z","updated_at":"2015-08-25T19:37:16Z","closed_at":null,"body":"Hi,\r\n\r\nI'm not sure how to give a reproducible example of this, so I apologize in advance ... I will try to give as much background as I can.\r\n\r\nI have a tst environment using shiny server community edition & whereas my dev & prod environments use shiny server pro.  The problem is that shiny-server COMMUNITY edition fails to load the packrat library, whereas shiny-server PRO edition succeeds in referencing the packrat library. \r\n\r\nI am logging this here because it would be very useful for shiny-server to make use of project-specific packrat libraries where they exist. I'm not sure exactly why this isn't working, except that the I have the PRO edition `utilization_scheduler` set to launch a new session for each connection, which may mean that each project gets initialized separately? \r\n\r\nThe community edition is: Shiny Server v1.4.0.721 (Node.js v0.10.21)\r\nThe pro edition is: Shiny Server (Commercial) v1.4.0.637 (Node.js v0.10.21)\r\nBoth are running on VMs with RHEL7 & they are otherwise similar builds. \r\n\r\n__ Background __ \r\nWe have several apps in deployment using gitlab-ci (EE) for deployment.  Each app uses packrat to isolate package-specific effects from the other projects. There is nothing other than packrat & shiny in the site-wide LIB for both boxes.\r\n\r\nIn this case, I have an identical app deployed to both boxes using the same gitlab-ci deploy script from the same commit hash.  \r\n\r\nOur deploy logs looks similar for the two builds, e.g.: \r\n\r\n```\r\nRemoving caTools ... OK\r\nRemoving gdata ... OK\r\nReplacing R6 (upgrade 2.1.0 to 2.1.1) ... \tOK (built source)\r\nReplacing dplyr (upgrade 0.4.2 to 0.4.2.9002) ... \tOK (built source)\r\nReplacing shiny (upgrade 0.12.1.9001 to 0.12.2) ... \tOK (built source)\r\nReplacing netezza (upgrade 0.6-3 to 0.6-3.1) ... \tOK (built source)\r\nUp to date.\r\n```\r\n\r\nYou may recognize the above as output from having run `packrat::restore()`\r\n\r\nAt any rate, when I browse to the app on the tst box which runs the community edition, I get a message `ERROR: there is no package called â€˜ggplot2â€™`. When I browse to the same app on our dev box which runs the pro edition, I see the app as expected.\r\n\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/rstudio/shiny-server/issues/comments/134711682","html_url":"https://github.com/rstudio/shiny-server/issues/143#issuecomment-134711682","issue_url":"https://api.github.com/repos/rstudio/shiny-server/issues/143","id":134711682,"user":{"login":"fereshtehRS","id":4906984,"avatar_url":"https://avatars.githubusercontent.com/u/4906984?v=3","gravatar_id":"","url":"https://api.github.com/users/fereshtehRS","html_url":"https://github.com/fereshtehRS","followers_url":"https://api.github.com/users/fereshtehRS/followers","following_url":"https://api.github.com/users/fereshtehRS/following{/other_user}","gists_url":"https://api.github.com/users/fereshtehRS/gists{/gist_id}","starred_url":"https://api.github.com/users/fereshtehRS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fereshtehRS/subscriptions","organizations_url":"https://api.github.com/users/fereshtehRS/orgs","repos_url":"https://api.github.com/users/fereshtehRS/repos","events_url":"https://api.github.com/users/fereshtehRS/events{/privacy}","received_events_url":"https://api.github.com/users/fereshtehRS/received_events","type":"User","site_admin":false},"created_at":"2015-08-25T19:37:16Z","updated_at":"2015-08-25T19:37:16Z","body":"Jacki, Your config files are fine. I just wanted to make sure you are using the same configuration in Pro and community setups.\r\n\r\nI see the same behavior as you explained. This seems to be related to the way R processes are initiated, which is different between the Pro and community versions. This is partly intentional, but we will look into it.\r\n\r\n"}}