Welcome to the frame wiki!

Goals

• Low-cost

A basic frame installation should be totally free, requiring just the lowest-tier web dyne, memcache, and redis environments.

• Scable

Start off on the free instance, ramp it up to high levels without having to touch code. Everything should be doable within the heroku configuration window

• One-click setup

Need to be able to deploy to heroku by pressing a button. EC2 deployment is something that we can ignore for now, but ideally we have a simple process for that as well (pre-built AMIs?)

• Language agnostic (ish)

You shouldn't need to know python to use frame. That means that it lives as a separate instance from the rest of your site, it works with ruby/python/node/html/net/mobile apps. You should be able to add features without having to code them yourself, which means that everything should be modular and installable through pip

• You retain ownership and control of everything

We use your S3 bucket. You host frame yourself. You can modify anything. License is flexible enough to allow you to fork and modify things

• Easy to Grep and exciting

The README doesn't suck; frame has a nice logo; the web interface is polished; there is 'frame in 60 seconds' video; screenshots of everything; live demo; one click install; concise overview and summary of features at the very top of readme

• Monitoring

You should to be able to know how frame is being used. If slowdowns occur, it should be obvious without having to resort to looking in a million different places. This means that cache info, number of uploads, variations, global size, requests should be visible within the web interface.

Possible goals

Frame becomes the easiest way to handle uploading and serving of all media files. That means images, videos, pdfs, files - anything that you would see in MEDIA_ROOT. Let's avoid this for now though.