-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: cron job for ensuring KWB computers have access to "stable" KWB-R packages #6
Comments
Didn`t remember but more or less solved in R package "pkgmeta": (slightly modified)
|
@ItAtKwb I now implemented a new function in kwb.package whith you could try out:
|
The solution for our @ItAtKwb could you modify
Below location
|
After phone call with @ItAtKwb today morning we defined to modify
Content of
Afterwards we can simply install and update our public R packages (available on https://kwb-r.r-universe.dev): InstallUpdate |
Takeaways after discussing with @ItAtKwb for 2 hours what can be improved after the flusshygiene cron-job crash after updating KWB`s linux server to R 4.0.1 and realizing the messy R library installation workflow (2 cron job, one by @ItAtKwb and @wseis use different R libraries !!!) we ended up with some centralisation approach, which will not rule out all further issues but may be harmonize the "general" deployment at KWB of R packages.
The idea is that we provide an R script that can be used by @ItAtKwb to run a daily cron job on Linux/Windows servers so that:
always contain the latest version of R packages (always) on the "master" branch precompiled for both "linux" and "windows" and the latest KWB R release (currently: 4.01).
For Windows @ItAtKwb proposed to adapt the .libPaths() variable .Renvironment file (could be "rolled" out by Marcus.
@hsonne what do you think????
Below a first incomplete and buggy first version how this could look like:
For linux the known system dependencies for package installation are described here:
https://github.com/KWB-R/pkgmeta/blob/master/.travis.yml#L9
The text was updated successfully, but these errors were encountered: