[cre, aut]A very flexible framework for building server side logic in R. The framework is unopinionated when it comes to how HTTP requests and WebSocket messages are handled and supports all levels of app complexity; from serving static content to full-blown dynamic web-apps. Fiery does not hold your hand as much as e.g. the shiny package does, but instead sets you free to create your web app the way you want.
| Version: | 1.1.2 |
| Imports: | R6, assertthat, httpuv, uuid, utils, stringi, future, later, stats, reqres, glue, crayon |
| Suggests: | testthat, covr, knitr, rmarkdown |
| Published: | 2019-09-27 |
| Author: | Thomas Lin Pedersen
[cre, aut] |
| Maintainer: | Thomas Lin Pedersen <thomasp85 at gmail.com> |
| BugReports: | https://github.com/thomasp85/fiery/issues |
| License: | MIT + file LICENSE |
| URL: | https://fiery.data-imaginist.com, https://github.com/thomasp85/fiery |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| In views: | WebTechnologies |
| CRAN checks: | fiery results |
| Reference manual: | fiery.pdf |
| Vignettes: |
Delaying code execution in Fiery The event cycle in fiery Creating and using fiery plugins |
| Package source: | fiery_1.1.2.tar.gz |
| Windows binaries: | r-devel: fiery_1.1.2.zip, r-release: fiery_1.1.2.zip, r-oldrel: fiery_1.1.2.zip |
| macOS binaries: | r-release: fiery_1.1.2.tgz, r-oldrel: fiery_1.1.2.tgz |
| Old sources: | fiery archive |
| Reverse imports: | dash |
| Reverse suggests: | reqres, routr |
Please use the canonical form https://CRAN.R-project.org/package=fiery to link to this page.