Recreating the conditions under which I get shiny to load has been, err, tricky. I tested this to death yesterday evening with no issues every time. I come back this morning and find your message
So you don't think I'm going bananas:
However, to get shiny lo load, I had to do something very odd.
All of my projects, live in a sub directory called projects on a development SD. As each one is completed, its sub directory project is moved into another sub directory called completed, which is within projects. If I need to work on a project, I move the appropriate project directory back to the projects directory. This approach is simply for organisation. All testing yesterday evening was done with the R project in projects (not completed), but only running from the pnd.
Once the updated pnd was uploaded, I moved the R project into the completed sub directory - as normal. HOWEVER, as a result of moving the project into the completed sub directory, I now find shiny will not load. Move the R project back, and bingo :blink:
Bear in mind here that I'm not actually running anything from the projects folder - well, not intentionally anyway. So where to now? Well, It looks like that when shiny was installed, a path was written - somewhere, that references the actual location of R whilst I was working on it. This was something I thought could happen, so when I work on R, I work through a sym link in /mnt/utmp/R - which points to the pnd sub directory. To all intents and purposes, I expected this sym link approach to negate problems like this. Clearly something has confounded this approach. I'll do some digging inside the shiny package and see if I can find the reference to the path........
