Sure, you can find it here:
https://github.com/dlindelof/run
On Fri, Feb 8, 2019 at 9:41 AM Rainer M Krug wrote:
> Sounds interesting. Do you have it on GitHub or similar?
>
> Rainer
>
> On 8 Feb 2019, at 09:09, David Lindelof wrote:
>
> Yesterday I wrote and submitted t
Yesterday I wrote and submitted to CRAN a package `run`, which implements
the ideas discussed in this thread. Given a package tarball
foo_0.1.0.tar.gz, users will be able to run
Rscript -e "run::run('foo_0.1.0.tar.gz')"
which will pull all the dependencies of package `foo`, lookup a function
`mai
I see some value in Duncan’s proposal to implement this as an extra package
instead of a change to base R, if only to see if the idea has legs. I’m
minded to do so myself using your suggestion, but is there a particular
reason why you recommend using the remotes package instead of devtools? The
lat
cies? Would it make sense to submit this as a desirable feature?
Cheers,
David
On Thu, Jan 31, 2019 at 4:38 PM Barry Rowlingson <
b.rowling...@lancaster.ac.uk> wrote:
>
>
> On Thu, Jan 31, 2019 at 3:14 PM David Lindelof wrote:
>
>>
>> In summary, I'm convinc
k> wrote:
>
>
> On Thu, Jan 31, 2019 at 3:14 PM David Lindelof wrote:
>
>>
>> In summary, I'm convinced R would benefit from something similar to Java's
>> `Main-Class` header or Python's `__main__()` function. A new R CMD command
>> wou
Belated thanks to all who replied to my initial query. In summary, three
approaches have been mentioned to run R code "in production": 1)
ShinyProxy, mentioned by Tobias, for deploying Shiny applications; 2)
Docker-like solutions, mentioned by Gergely and Iñaki; and 3) Solutions
based on Rscript or
Dear all,
I’m working as a data scientist in a major tech company. I have been using
R for almost 20 years now and there’s one issue that’s been bugging me of
late. I apologize in advance if this has been discussed before.
R has traditionally been used for running short scripts or data analysis
n
