如何从OSX终端运行R Shiny App？

Got it, let's work through creating a working command file for your ngram-shiny app. Since you already have it up and running manually, we just need to translate that manual process into a repeatable script. Here are tailored solutions based on your operating system, plus troubleshooting tips to fix common snags:

This is the go-to for Unix-like systems. Follow these steps:

• Create a new file named start-ngram-app.sh (you can use touch start-ngram-app.sh in terminal)
• Open it with a text editor and paste this code, replacing placeholders with your actual paths:

#!/bin/bash

# If Rscript is already in your system PATH, you can skip defining RSCRIPT_PATH
RSCRIPT_PATH="/usr/bin/Rscript"

# Replace the app path with the absolute path to your ngram-shiny-app directory
$RSCRIPT_PATH -e 'shiny::runApp("/full/path/to/ngram-shiny-app", port = 3838, host = "0.0.0.0")'

• Make the script executable by running: chmod +x start-ngram-app.sh
• Launch the app anytime with: ./start-ngram-app.sh

For Windows systems, a batch file will do the trick:

• Right-click in your app directory > New > Text Document, rename it to start-ngram-app.bat (make sure file extensions are visible)
• Open it with Notepad and paste this code, updating paths to match your setup:

@echo off
REM Replace with your Rscript installation path (adjust the R version number as needed)
set RSCRIPT_PATH="C:\Program Files\R\R-4.3.1\bin\Rscript.exe"
REM Use double backslashes for Windows paths
%RSCRIPT_PATH% -e "shiny::runApp('C:\\full\\path\\to\\ngram-shiny-app', port = 3838, host = '0.0.0.0')"
pause

• Double-click the .bat file to launch the app, or run it from Command Prompt.

If your script still isn't working, check these common culprits:

• Incorrect paths: Always use absolute paths for both Rscript and the app directory. Windows requires double backslashes (\\) while Unix uses single forward slashes (/).
• Port conflicts: If you get a "port already in use" error, change the port value in the script (e.g., 3839 instead of 3838).
• R environment mismatches: Sometimes scripts use a different R environment than your manual session. Add explicit library loads at the start of the R command if needed, like:

  $RSCRIPT_PATH -e 'library(shiny); library(ngram); shiny::runApp("/path/to/app")'
  

• Background running (Unix only): To keep the app running after closing the terminal, modify the script to use nohup:

  nohup $RSCRIPT_PATH -e 'shiny::runApp("/path/to/app")' > app.log 2>&1 &
  

  This logs output to app.log and runs the app in the background.

内容的提问来源于stack exchange，提问作者elliot