gambaroff / publicvoid Goto Github PK

Provide a UI so they can:
View their uploaded files
Upload

Replace the "Choose File" dialog in #5

Use S3 object storage when saving files. Sign up for an S3 account, and hardcode the credentials in rails config. Make sure the live credentials to AWS aren't committed in this public git repository (add to gitignore).

There is some security stuff, see: http://aws.amazon.com/articles/1434

Keeps spammers off site.

See Ch 16 of Agile Web Dev Rails 4 book.

Add the capability to make an administrative user. The first user created in the system is automatically the administrator. When another user signs up, the administrator can accept or reject the user, and also make them the administrator.

Allows independent content producers to serve video to consumers in a way similar to bittorent but can provide DRM. The publicvoid social network also forms a web of trust through social proof (people vouch for each other). Consumers pay a discount by being a part of the platform and devoting their disk space and bandwidth. Also provide a means to distribute/precache specific content from creators that they follow. Allow attaching multiple devices on your network for attached / detached storage (usb). Even allow real time cell phone upload from cell phones to the distribution network (live sports during blackout).

After creating an account #1, and before seeing the authenticated users landing page #12, users must log in. On failure, see #19.

Describe to the user in a visually-appealing manner what the site is and how to use it.

On signup, users must authenticate their emails before they can use the service.

This will replace Heroku as a deployment system.
Create an AWS account, locate the AWS credentials needed to post files programmatically to S3.
Start an Ubuntu Linux EC2 instance and SSH into it. You'll need an elastic IP and a DNS address record from your domain name attached to that elastic IP.
Install ruby, rvm. Use apt-get as appropriate.
Start a PostgreSQL RDS instance and configure the project to use that instance.
Be careful not to commit any config files that have FQDN of DB /ip addreses/ user/ passwords/ AWS secrets. Instead, add those files to gitignore.
Write a pure ruby script that asks the person setting up the instance for all of the necessary config params and writes them to the right file, runs gem install, rails start, etc.
Don't forget to stop instances every day when you're done with them 👍

Provide a logout button. This will destroy the client cookie.

There is a choose file button. The file gets saved on the server.

After uploading and moving files to Glacier, remove old files from S3. Also conduct delete per #15 (download from Glacier to S3)
Depends on #13

Change their name, email, password. Also provide a link from the "authenticated users page."

Modify download so files are retrieved from Glacier put into S3 for download once within 24 hours.

Do creative discovery. As a result of discovery, prepare a clear creative brief.

For example, we should consider doing the following.
Get rid of the following UI elements: Home, Help, Users, About, Contact, News.
Add Upload and Download (Download shows files already uploaded).

Users like client side checks so they don't have to wait to see if the info they put into in our form is valid. Resolve this limitation from #1.

Files are moved in and out of S3 to Glacier.

Add a meaningful README that reflects what we're trying to do.

Keep track of the space used by users, and bill them based on their storage and transfer. PayPal integration.

As a user, I can create an account for myself. I'll be asked for my name, email, and a password (+password confirm).

For simplicity, use server-side checks that passwords are same, valid and email address provided is valid.

This is going to be the first user story of the project. As a part of this user story, start with the basic rails app structure.