Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

start_rmote(server_dir) doesn't seem to work with ~/some_path #10

Open
lcolladotor opened this issue Feb 16, 2018 · 0 comments
Open

start_rmote(server_dir) doesn't seem to work with ~/some_path #10

lcolladotor opened this issue Feb 16, 2018 · 0 comments

Comments

@lcolladotor
Copy link

Hi,

While trying to get rmote working in an SGE cluster, I tried setting the server_dir argument to a value that would change by day and use a directory that could be accessed through multiple terminal sessions to SGE. So I tried setting server_dir to something like server_dir = paste0('~/rmote/rmote_server_', Sys.Date()) and it initially seemed to work (rmote printed the message with the url) but eventually it wasn't working. That's why I changed my .Rprofile to use /users/my_username/ instead of ~/ and it all worked after that point and now it also prints the To stop the server message. To make the difference in messages clear, I'm posting them here:

Failing with ~/

Serving the directory /users/my_username/rmote/rmote_server_2018_02_16 at http://127.0.0.1:4321

When it works:

Serving the directory /users/my_username/rmote/rmote_server_2018_02_16 at http://127.0.0.1:4321
To stop the server, run servr::daemon_stop("some_number") or restart your R session

I ignore if that's something you would expect or if you meant to have it work with paths that include ~/.

Best,
Leo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant