https://github.com/1egoman/todotxtaas

todo.txt as a service - hack upstate spring 2015 and winner of mongodb prize (oculus rift!)
https://github.com/1egoman/todotxtaas

Last synced: about 1 month ago
JSON representation

todo.txt as a service - hack upstate spring 2015 and winner of mongodb prize (oculus rift!)

• Host: GitHub
• URL: https://github.com/1egoman/todotxtaas
• Owner: 1egoman
• Created: 2015-03-22T15:08:14.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2015-06-24T17:25:08.000Z (over 9 years ago)
• Last Synced: 2024-04-11T13:59:59.575Z (9 months ago)
• Language: JavaScript
• Homepage: http://todotxtaas.ngrok.com
• Size: 828 KB
• Stars: 0
• Watchers: 5
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
TODOTXTaaS

===

My Hack Upstate Idea

Basically, write an app to fix the dropbox syncing problem of todo.txt.

The idea is to write a service that has standard CRUD operations for each item, and integrates well

with todo.txt projects and contexts. Also, there probably should be a frontend of some sort for the

whole thing, ala bootstrap.

Reference: https://github.com/ginatrapani/todo.txt-cli/wiki/The-Todo.txt-Format

NOTE: date is only set once items are completed

### GET /items

Outputs the full todo.txt file.

```

GET /items

(A) Thank Mom for the meatballs @phone

(B) Schedule Goodwill pickup +GarageSale @phone

Post signs around the neighborhood +GarageSale

@GroceryStore Eskimo pies

```

### GET /items/:selector

Outputs all items that match the selector(s). These can take the form of:

  - `@context` - search for all items with a context of `@context`

  - `+project` - search for all items with a project of `+project`

  - `text` - search in the item body for `text` (not case sensitive)

```

GET /items/@phone

(A) Thank Mom for the meatballs @phone

(B) Schedule Goodwill pickup +GarageSale @phone

GET /items/@phone/mom

(A) Thank Mom for the meatballs @phone

```

### POST /items

Adds a new item. The request body should contain the list item in todo.txt format.

```

POST /items

@GroceryStore milk

{

  "status": "OK",

  "method": "create",

  "msg": "Added new todo item: @GroceryStore milk"

}

```

### PUT /items/:id

updates item with the specified id (the `_id`)

### DELETE /items/:id

deletes item with the specified id (the `_id`)

### DELETE /items/:selector

  - destroy (Not implemented yet)