mirror of
https://github.com/rstudio/shiny.git
synced 2026-01-14 09:28:02 -05:00
"Package has help file(s) containing install/render-stage \Sexpr{} expressions but no prebuilt PDF manual."
59 lines
2.0 KiB
R
59 lines
2.0 KiB
R
% Generated by roxygen2: do not edit by hand
|
|
% Please edit documentation in R/server.R
|
|
\name{shinyServer}
|
|
\alias{shinyServer}
|
|
\title{Define Server Functionality}
|
|
\usage{
|
|
shinyServer(func)
|
|
}
|
|
\arguments{
|
|
\item{func}{The server function for this application. See the details section
|
|
for more information.}
|
|
}
|
|
\description{
|
|
\ifelse{html}{\href{https://lifecycle.r-lib.org/articles/stages.html#superseded}{\figure{lifecycle-superseded.svg}{options: alt='[Superseded]'}}}{\strong{[Superseded]}}
|
|
|
|
Defines the server-side logic of the Shiny application. This generally
|
|
involves creating functions that map user inputs to various kinds of output.
|
|
In older versions of Shiny, it was necessary to call \code{shinyServer()} in
|
|
the \code{server.R} file, but this is no longer required as of Shiny 0.10.
|
|
Now the \code{server.R} file may simply return the appropriate server
|
|
function (as the last expression in the code), without calling
|
|
\code{shinyServer()}.
|
|
|
|
Call \code{shinyServer} from your application's \code{server.R}
|
|
file, passing in a "server function" that provides the server-side logic of
|
|
your application.
|
|
|
|
The server function will be called when each client (web browser) first loads
|
|
the Shiny application's page. It must take an \code{input} and an
|
|
\code{output} parameter. Any return value will be ignored. It also takes an
|
|
optional \code{session} parameter, which is used when greater control is
|
|
needed.
|
|
|
|
See the \href{https://shiny.rstudio.com/tutorial/}{tutorial} for more
|
|
on how to write a server function.
|
|
}
|
|
\examples{
|
|
\dontrun{
|
|
# A very simple Shiny app that takes a message from the user
|
|
# and outputs an uppercase version of it.
|
|
shinyServer(function(input, output, session) {
|
|
output$uppercase <- renderText({
|
|
toupper(input$message)
|
|
})
|
|
})
|
|
|
|
|
|
# It is also possible for a server.R file to simply return the function,
|
|
# without calling shinyServer().
|
|
# For example, the server.R file could contain just the following:
|
|
function(input, output, session) {
|
|
output$uppercase <- renderText({
|
|
toupper(input$message)
|
|
})
|
|
}
|
|
}
|
|
}
|
|
\keyword{internal}
|