MyNixOS website logo
Description

Run Reports, Models, and Scripts from a Mobile Device.

A framework for interacting with R modules such as Reports, Models, and Scripts from a mobile device. The framework allows you to list available modules and select a module of interest using a basic e-mail interface. After selecting a specific module, you can either run it as is or provide input via the e-mail interface. After parsing your request, R will send the results back to your mobile device.

MobileTrigger

The MobileTrigger package allows you to access to R Models, Scripts, and Reports when you only have a mobile device with e-mail capabilities on hand. Here is a visual summary:

Mobile Device R data process flow

Installation

  • cran: install.package("MobileTrigger") (Coming Soon)
  • github: devtools::install_github("kenithgrey/MobileTrigger")

Basic Process Flow

Below is an overview. More extensive instructions can be found at https://r-bar.net/.

  1. Install the Package
  2. Define a Trigger root path (E.g., C:)
  3. Run the following R script to setup the folder structure. You will need to change the quoted items to fit your situation.
    
    #################################
    # Setting of MobileTriggers     #
    #################################
    
    ## OUTLOOK Style (uses tls = TRUE argument) ###
    SetupWindowsTrigger(path="c:/triggers",
                        Mail.To = "[email protected]",
                        Mail.From = "[email protected]",
                        SMTP.Settings=list(
                        host.name = 'smtp.office365.com',
                        port = 587,
                        user.name = '[email protected]',
                        passwd = 'password', tls = TRUE)
     )
    
     ## Other STYLE (uses ssl = TRUE argument) ###
     SetupWindowsTrigger(path="c:/triggers",
                         Mail.To = "[email protected]",
                         Mail.From = "[email protected]",
                         SMTP.Settings=list(
                             host.name = 'some.smtp.sever.com',
                             port = 587,
                             user.name = '[email protected]',
                             passwd = 'password', ssl = TRUE)
     )
    
  4. Locate the starterMessages.bat file in the Trigger root path. This will launch the starterMessages.R file in headless mode. After running the batch file, 6 Messages with different subjects will be sent to the target e-mail box in step 3. Use these to setup your e-mail rules.
  5. Setup E-mail rules:
    1. Outlook You will need to make a small windows registry adjustment to allow OUTLOOK rules to run VBA script. The VBA scripts you need are located in the OUTLOOK.txt file in the Trigger root folder. They are very simple. They either write a message to txt or run an R script in headless mode. When you have the VBA in, Connect each starter messages from step 4 with the appropriate VBA function. Click here for more detailed instructions
    2. ThunderBird You will need to download the FiltaQuila plugin for ThunderBird. Once installed, adjust the FiltaQuilla settings to allow saving email messages to text files. The text files will need to be saved in the Trigger root folder. Click here for more detailed instructions.
  6. If the rules are setup correctly when you send an e-mail from the FROM e-mail account in step 3, you will depending on the SUBJECT line:
    1. List out the available Models, Scripts, or Reports
    2. Run the available Models, Scripts, or Reports.
Again, more detailed instructions can be found at
Metadata

Version

0.0.31

License

Unknown

Platforms (75)

    Darwin
    FreeBSD
    Genode
    GHCJS
    Linux
    MMIXware
    NetBSD
    none
    OpenBSD
    Redox
    Solaris
    WASI
    Windows
Show all
  • aarch64-darwin
  • aarch64-genode
  • aarch64-linux
  • aarch64-netbsd
  • aarch64-none
  • aarch64_be-none
  • arm-none
  • armv5tel-linux
  • armv6l-linux
  • armv6l-netbsd
  • armv6l-none
  • armv7a-darwin
  • armv7a-linux
  • armv7a-netbsd
  • armv7l-linux
  • armv7l-netbsd
  • avr-none
  • i686-cygwin
  • i686-darwin
  • i686-freebsd
  • i686-genode
  • i686-linux
  • i686-netbsd
  • i686-none
  • i686-openbsd
  • i686-windows
  • javascript-ghcjs
  • loongarch64-linux
  • m68k-linux
  • m68k-netbsd
  • m68k-none
  • microblaze-linux
  • microblaze-none
  • microblazeel-linux
  • microblazeel-none
  • mips-linux
  • mips-none
  • mips64-linux
  • mips64-none
  • mips64el-linux
  • mipsel-linux
  • mipsel-netbsd
  • mmix-mmixware
  • msp430-none
  • or1k-none
  • powerpc-netbsd
  • powerpc-none
  • powerpc64-linux
  • powerpc64le-linux
  • powerpcle-none
  • riscv32-linux
  • riscv32-netbsd
  • riscv32-none
  • riscv64-linux
  • riscv64-netbsd
  • riscv64-none
  • rx-none
  • s390-linux
  • s390-none
  • s390x-linux
  • s390x-none
  • vc4-none
  • wasm32-wasi
  • wasm64-wasi
  • x86_64-cygwin
  • x86_64-darwin
  • x86_64-freebsd
  • x86_64-genode
  • x86_64-linux
  • x86_64-netbsd
  • x86_64-none
  • x86_64-openbsd
  • x86_64-redox
  • x86_64-solaris
  • x86_64-windows