https://github.com/Athospd/targetsboard
A GUI to {targets}. An alternative to tar_watch().
https://github.com/Athospd/targetsboard
Last synced: 2 months ago
JSON representation
A GUI to {targets}. An alternative to tar_watch().
- Host: GitHub
- URL: https://github.com/Athospd/targetsboard
- Owner: Athospd
- License: other
- Created: 2024-11-17T06:17:55.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2024-11-17T06:21:02.000Z (3 months ago)
- Last Synced: 2024-11-17T07:27:39.727Z (3 months ago)
- Language: JavaScript
- Size: 925 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.Rmd
- License: LICENSE
Awesome Lists containing this project
- jimsghstars - Athospd/targetsboard - A GUI to {targets}. An alternative to tar_watch(). (JavaScript)
README
---
output: github_document
---
```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
fig.path = "man/figures/README-",
out.width = "100%"
)
```
# targetsboard
[](https://lifecycle.r-lib.org/articles/stages.html#experimental)
An experimental alternative to `targets::tar_watch()` to monitor and (eventually) control DAGs from the UI.
**Ultra-early stage**! Still finding out if any useful. Help/Support/Ideas are welcomed!
## Installation
You can install the development version of targetsboard like so:
```r
remotes::install_github("Athospd/targetsboard")
```
## Usage
In your normal, day-to-day targets workflow, launch the targetsboard through `tar_board()`.
```{r example, eval = FALSE}
library(targetsboard)
# launch the app
app <- tar_board()
```
```r
# go to localhost:9999 where the board is being served
browseURL("http://localhost:9999")
# you can check it is alive, running on background
app$is_alive()
```
It will keep track of your targets' metadata just like `tar_watch()` would do.
```{r make, eval = FALSE}
tar_make()
# tar_destroy()
# tar_invalidate()
# tar_read()
# tar_... and so on
```
```{r kill, eval = FALSE}
# you can eventually shut the app down like so
app$kill()
```