{"id":15650223,"url":"https://github.com/bachya/sifttter-redux","last_synced_at":"2025-08-13T15:49:10.935Z","repository":{"id":13805425,"uuid":"16501339","full_name":"bachya/Sifttter-Redux","owner":"bachya","description":"IFTTT to Day One service","archived":false,"fork":false,"pushed_at":"2021-12-02T21:01:54.000Z","size":234,"stargazers_count":35,"open_issues_count":10,"forks_count":0,"subscribers_count":8,"default_branch":"master","last_synced_at":"2025-07-28T15:10:52.889Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Ruby","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bachya.png","metadata":{"files":{"readme":"README.md","changelog":"HISTORY.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-02-04T03:33:34.000Z","updated_at":"2024-09-30T21:32:10.000Z","dependencies_parsed_at":"2022-09-06T12:21:01.437Z","dependency_job_id":null,"html_url":"https://github.com/bachya/Sifttter-Redux","commit_stats":null,"previous_names":[],"tags_count":12,"template":false,"template_full_name":null,"purl":"pkg:github/bachya/Sifttter-Redux","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bachya%2FSifttter-Redux","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bachya%2FSifttter-Redux/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bachya%2FSifttter-Redux/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bachya%2FSifttter-Redux/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bachya","download_url":"https://codeload.github.com/bachya/Sifttter-Redux/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bachya%2FSifttter-Redux/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":270268636,"owners_count":24555643,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-13T02:00:09.904Z","response_time":66,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-03T12:34:02.347Z","updated_at":"2025-08-13T15:49:10.888Z","avatar_url":"https://github.com/bachya.png","language":"Ruby","funding_links":[],"categories":[],"sub_categories":[],"readme":"Sifttter Redux\n==============\n[![Build Status](https://travis-ci.org/bachya/Sifttter-Redux.svg?branch=master)](https://travis-ci.org/bachya/Sifttter-Redux)\n[![Gem Version](https://badge.fury.io/rb/sifttter-redux.svg)](http://badge.fury.io/rb/sifttter-redux)\n\n# Upgrading From 0.x.x to 1.0.0?\n\nMake sure you read the [IFTTT Template](#ifttt-template) section.\n\n# Intro\n\nSiftter Redux is a modification of Craig Eley's\n[Sifttter](http://craigeley.com/post/72565974459/sifttter-an-ifttt-to-day-one-logger \"Sifttter\"),\na script to collect information from [IFTTT](http://www.ifttt.com \"IFTTT\") and\nplace it in a [Day One](http://dayoneapp.com, \"Day One\") journal.\n\nSiftter Redux has several fundamental differences:\n\n* Interactive logging of today's events or events in the past\n* \"Catch Up\" mode for logging several days' events at once\n* Packaged as a command line app, complete with documentation and help\n* Easy installation on cron for automated running\n\n# Prerequisites\n\nIn addition to Git (which, given you being on this site, I'll assume you have),\nRuby (v. 1.9.3 or greater) is needed.\n\n# Installation\n\n```\ngem install sifttter-redux\n```\n\n# Usage\n\nSyntax and usage can be accessed by running `srd help`:\n\n```\n$ srd help\nNAME\n    srd - Sifttter Redux\n\n    A customized IFTTT-to-Day One service that allows for\n    smart installation and automated running on a standalone\n    *NIX device (such as a Raspberry Pi).\n\nSYNOPSIS\n    srd [global options] command [command options] [arguments...]\n\nVERSION\n   1.0.6\n\nGLOBAL OPTIONS\n    --help         - Show this message\n    --[no-]verbose - Turns on verbose output\n    --version      - Display the program version\n\nCOMMANDS\n    exec - Execute the script\n    help - Shows a list of commands or help for one command\n    init - Install and initialize dependencies\n```\n\nNote that each command's options can be revealed by adding the `--help` switch\nafter the command. For example:\n\n```\n$ srd exec --help\nNAME\n    exec - Execute the script\n\nSYNOPSIS\n    srd [global options] exec [command options]\n\nCOMMAND OPTIONS\n    -c             - Run catch-up mode from the beginning of the week to yesterday\n    -f arg         - Run catch-up mode with this start date (default: none)\n    -i             - Include today's date in catch-up\n    -n arg         - Run catch-up mode for the last N days (default: none)\n    -t arg         - Run catch-up mode with this end date (must also have -f) (default: none)\n    --[no-]verbose - Turns on verbose output\n    -w arg         - Run catch-up mode for the last N weeks (default: none)\n    -y             - Run catch-up mode for yesterday\n```\n\n## IFTTT Template\n\nVersion 1.0.0+ uses a new schema that allows for any type of Markdown. Thus, Sifttter\nfiles from IFTTT need to follow this format:\n\n```\n@begin\n@date April 21, 2014 at 12:34PM\n**Any** sort of *Markdown* goes here...\n@end\n```\n\nWhereas the previous Sifttter Redux only allowed output of bulleted lists, this new \ntemplate style allows you to include *any* Markdown, making output like tables possibe.\n\n### Upgrade Command\n\nNote that a new command has been introduced that attempts to upgrade to this\nnew format. **Although the command backs up your current Sifttter files, you\nare strongly encouraged to make a separate, manual backup.**\n\n```Bash\n$ srd upgrade\n```\n\n### Template Tokens\n\nIFTTT templates can make use of the following tokens:\n\n* `%time%`: the time the entry was created\n\nAs an example, to include the entry time in a template:\n\n```\n@begin\n@date April 21, 2014 at 12:34PM\n- %time%: My text goes here...\n@end\n```\n\n## Initialization\n\n```\n$ srd init\n```\n\nInitialization will perform the following steps:\n\n1. Download [Dropbox Uploader](https://github.com/andreafabrizi/Dropbox-Uploader \"Dropbox-Uploder\")\nto a location of your choice.\n2. Automatically configure Dropbox Uploader.\n3. Collect some user paths (note that you can use tab completion here!):\n * The location on your filesystem where Sifttter files will be temporarily stored\n * The location of your Sifttter files in Dropbox\n * The location on your filesystem where Day One files will be temporarily stored\n * The location of your Day One files in Dropbox\n\n## Pathing\n\nNote that when Sifttter Redux asks you for paths, it will ask for \"local\" and\n\"remote\" filepaths. It's important to understand the difference.\n\n### Local Filepaths\n\nLocal filepaths are, as you'd expect, filepaths on your local machine. Some\nexamples might be:\n\n* `/tmp/my_data`\n* `/home/bob/ifttt/sifttter_data`\n* `~/sifttter`\n\n### Remote Filepaths\n\nRemote filepaths, on the other hand, are absolute filepaths in your Dropbox\nfolder (*as Dropbox Uploader would see them*). For instance,\n`/home/bob/Dropbox/apps/sifttter` is *not* a valid remote filepath; rather,\n`/apps/sifttter` would be correct.\n\n## Basic Execution\n\n```\n$ srd exec\n#### EXECUTING...\n---\u003e INFO: Creating entry for February 15, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 15, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\n## \"Catch-up\" Mode\n\nSometimes, events occur that prevent Sifttter Redux from running (power loss to\n  your device, a bad Cron job, etc.). In this case, Sifttter Redux's \"catch-up\"\n  mode can be used to collect any valid journal on or before today's date.\n\nThere are many ways to use this mode (note that \"today\" in these examples is\n**February 15, 2014**):\n\n### Yesterday Catch-up\n\nTo create an entry for yesterday:\n\n```\n$ srd exec -y\n#### EXECUTING...\n---\u003e INFO: Creating entry for February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\n### Catch-up for a Specific Date\n\nTo create an entry for specific date:\n\n```\n$ srd exec -d 2014-02-14\n#### EXECUTING...\n---\u003e INFO: Creating entry for February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\n### Last \"N\" Days Catch-up\n\nSifttter Redux allows you to specify the number of days back it should look for\nnew entries:\n\n```\n$ srd exec -n 3\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 12, 2014 to February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n\n$ srd exec -n 12\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 03, 2014 to February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: February 03, 2014...\n---\u003e SUCCESS: February 04, 2014...\n---\u003e SUCCESS: February 05, 2014...\n---\u003e SUCCESS: February 06, 2014...\n---\u003e SUCCESS: February 07, 2014...\n---\u003e SUCCESS: February 08, 2014...\n---\u003e SUCCESS: February 09, 2014...\n---\u003e SUCCESS: February 10, 2014...\n---\u003e SUCCESS: February 11, 2014...\n---\u003e SUCCESS: February 12, 2014...\n---\u003e SUCCESS: February 13, 2014...\n---\u003e SUCCESS: February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nNote that this option goes until yesterday (\"yesterday\" because you might not be\nready to have today's entries scanned). If you'd rather include today's date, you\ncan always add the `-i` switch:\n\n```\n$ srd exec -i -n 3\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 12, 2014 to February 15, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e SUCCESS: Entry logged for February 15, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\n### Last \"N\" Weeks Catch-up\n\nSifttter Redux also allows you to specify a number of weeks back that should be\nscanned for new entries:\n\n```\n$ srd exec -w 1\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 03, 2014 to February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n\n$ srd exec -w 3\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from January 20, 2014 to February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for January 20, 2014...\n---\u003e SUCCESS: Entry logged for January 21, 2014...\n---\u003e SUCCESS: Entry logged for January 22, 2014...\n---\u003e SUCCESS: Entry logged for January 23, 2014...\n---\u003e SUCCESS: Entry logged for January 24, 2014...\n---\u003e SUCCESS: Entry logged for January 25, 2014...\n---\u003e SUCCESS: Entry logged for January 26, 2014...\n---\u003e SUCCESS: Entry logged for January 27, 2014...\n---\u003e SUCCESS: Entry logged for January 28, 2014...\n---\u003e SUCCESS: Entry logged for January 29, 2014...\n---\u003e SUCCESS: Entry logged for January 30, 2014...\n---\u003e SUCCESS: Entry logged for January 31, 2014...\n---\u003e SUCCESS: Entry logged for February 01, 2014...\n---\u003e SUCCESS: Entry logged for February 02, 2014...\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nAs you'd expect, you can always add the `-i` switch:\n\n```\n$ srd exec -i -w 1\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 03, 2014 to February 15, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e SUCCESS: Entry logged for February 15, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\n### Date Range Catch-up\n\nTo create entries for a range of dates:\n\n```\n$ srd exec -f 2014-02-01 -t 2014-02-12\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 01, 2014 to February 12, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 01, 2014...\n---\u003e SUCCESS: Entry logged for February 02, 2014...\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nEven more simply, to create entries from a specific point until yesterday\n(\"yesterday\" because you might not be ready to have today's entries scanned):\n\n```\n$ srd exec -f 2014-02-01\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 01, 2014 to February 12, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 01, 2014...\n---\u003e SUCCESS: Entry logged for February 02, 2014...\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nIn this case, once more, you can use the trusty `-i` switch if you want:\n\n```\n$ srd exec -i -f 2014-02-01\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 01, 2014 to February 15, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 01, 2014...\n---\u003e SUCCESS: Entry logged for February 02, 2014...\n---\u003e SUCCESS: Entry logged for February 03, 2014...\n---\u003e SUCCESS: Entry logged for February 04, 2014...\n---\u003e SUCCESS: Entry logged for February 05, 2014...\n---\u003e SUCCESS: Entry logged for February 06, 2014...\n---\u003e SUCCESS: Entry logged for February 07, 2014...\n---\u003e SUCCESS: Entry logged for February 08, 2014...\n---\u003e SUCCESS: Entry logged for February 09, 2014...\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e SUCCESS: Entry logged for February 15, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nTwo notes to be aware of:\n\n* `-f` and `-t` are *inclusive* parameters, meaning that when specified, those\ndates will be included when searching for Siftter data.\n* Although you can specify `-f` by itself, you cannot specify `-t` by itself.\n\nSifttter Redux makes use of the excellent\n[Chronic gem](https://github.com/mojombo/chronic \"Chronic\"), which provides\nnatural language parsing for dates and times. This means that you can run\ncommands with more \"human\" dates:\n\n```\n$ srd exec -f \"last monday\" -t \"yesterday\"\n#### EXECUTING...\n---\u003e INFO: Creating entries for dates from February 10, 2014 to February 14, 2014...\n---\u003e INFO: Downloading Sifttter files...DONE.\n---\u003e SUCCESS: Entry logged for February 10, 2014...\n---\u003e SUCCESS: Entry logged for February 11, 2014...\n---\u003e SUCCESS: Entry logged for February 12, 2014...\n---\u003e SUCCESS: Entry logged for February 13, 2014...\n---\u003e SUCCESS: Entry logged for February 14, 2014...\n---\u003e INFO: Uploading Day One entries to Dropbox...DONE.\n---\u003e INFO: Removing downloaded Day One files...DONE.\n---\u003e INFO: Removing downloaded Sifttter files...DONE.\n#### EXECUTION COMPLETE!\n```\n\nSee [Chronic's Examples section](https://github.com/mojombo/chronic#examples \"Chronic Examples\")\nfor more examples.\n\n# Cron Job\n\nBy installing an entry to a `crontab`, Sifttter Redux can be run automatically\non a schedule. The aim of this project was to use a Raspberry Pi; as such, the\ninstructions below are specifically catered to that platform. That said, it\nshould be possible to install and configure on any *NIX platform.\n\nOne issue that arises is the loading of the bundled gems; because cron runs in a\nlimited environment, it does not automatically know where to find installed gems.\n\n## Using RVM\n\nIf your Raspberry Pi uses RVM, this `crontab` entry will do:\n\n```\n55 23 * * * /bin/bash -l -c 'source \"$HOME/.rvm/scripts/rvm\" \u0026\u0026 srd exec'\n```\n\n## Globally Installing Bundled Gems\n\nAnother option is to install the bundled gems to the global gemset:\n\n```\n$ bundle install --global\n```\n\n# Logging\n\nSifttter Redux logs a lot of good info to `~/.sifttter_redux_log`. It makes use\nof Ruby's standard log levels:\n\n* DEBUG\n* INFO\n* WARN\n* ERROR\n* FATAL\n* UNKNOWN\n\nIf you want to see more or less in your log files, simply change the `log_level`\nvalue in `~/.sifttter_redux` to your desired level.\n\n# Bugs and Feature Requests\n\nMy current roadmap can be found on my\n[Trello board](https://trello.com/b/z4vl3YxC/sifttter-redux \"Sifttter Redux Trello Board\").\n\nTo report bugs with or suggest features/changes for Sifttter Redux, please use\nthe [Issues Page](http://github.com/bachya/sifttter-redux/issues).\n\nContributions are welcome and encouraged. To contribute:\n\n* [Fork Sifttter Redux](http://github.com/bachya/sifttter-redux/fork).\n* Create a branch for your contribution (`git checkout -b new-feature`).\n* Commit your changes (`git commit -am 'Added this new feature'`).\n* Push to the branch (`git push origin new-feature`).\n* Create a new [Pull Request](http://github.com/bachya/sifttter-redux/compare/).\n\n# License\n\n(The MIT License)\n\nCopyright © 2014 Aaron Bach \u003cbachya1208@gmail.com\u003e\n\nPermission is hereby granted, free of charge, to any person obtaining a copy of\nthis software and associated documentation files (the 'Software'), to deal in the\nSoftware without restriction, including without limitation the rights to use,\ncopy, modify, merge, publish, distribute, sublicense, and/or sell copies of the\nSoftware, and to permit persons to whom the Software is furnished to do so,\nsubject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS\nFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR\nCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER\nIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION\nWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\n\n# Credits\n\n* Craig Eley for [Sifttter](http://craigeley.com/post/72565974459/sifttter-an-ifttt-to-day-one-logger \"Sifttter\")\nand for giving me the idea for Sifttter Redux\n* Dave Copeland for [GLI](https://github.com/davetron5000/gli \"GLI\")\n* Andrea Fabrizi for [Dropbox Uploader](https://github.com/andreafabrizi/Dropbox-Uploader \"Dropbox Uploader\")\n* ~~Tom Preston-Werner~~ (sorry: can't\nsupport [harrassment](http://www.businessinsider.com/github-co-founder-suspended-2014-3 \"GitHub Founder Tom Preston-Werner Suspended After Harassment Allegations\"))\n~~and~~ Lee Jarvis for [Chronic](https://github.com/mojombo/chronic \"Chronic\")\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbachya%2Fsifttter-redux","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbachya%2Fsifttter-redux","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbachya%2Fsifttter-redux/lists"}