DuckCloud File Management System

A web application by SquishyDucks

• Deployed Front-End: https://howardreith.github.io/DuckCloud_FrontEnd/
• Deployed Back-End: https://thawing-badlands-39694.herokuapp.com/
• Front-End Repo: https://github.com/howardreith/DuckCloud_FrontEnd
• Back-End Repo: https://github.com/howardreith/DuckCloud_BackEnd

DuckCloud is a file management system allowing users to upload, store, and retrieve files. The application displays meta-data related to the files including title, creation date/time, and update date/time. Users can create, update, and delete files they own and download/view any file uploaded by any user.

DuckCloud makes use of HTML, CSS, Javascript, JQuery, Handlebars, Bootstrap, Node, MongoDB, Mongoose, and Express.

Development Process

Planning

To plan our project, we began by creating a "To-Do" list of every step we anticipated having to take to achieve a finished product. We broke down each step as minutely as we could so as to help clarify what precisely needed to be achieved at each stage. This was also helpful in determining at what points we should commit, push, and deploy our code.

The To-Do list is available here: https://docs.google.com/document/d/1b5cyE8ktW0przQeRlUCJxyn1mr2MOaJu1rVCXaip7R4/edit

Process

As we uncovered tasks we had not anticipated, we added these items to the To-Do list. As we continued, we found it more useful to use the Github issue queue to specify required changed as opposed to relying on the Google Doc.

As we completed each task we each volunteered to take on a subsequent one on the list or in the issue queue. If a task involved code developed by more than one of us, we would collaborate, usually no more than two to a task so we could always be working on multiple problems at once.

At major successes, and every few hours (usually 3-4 times per day) we got together and did a carefully-controlled merge to make sure our code meshed together without breaking anything. When merge conflicts arose, one of the coders most familiar with the merging code resolved the conflict and then another reviewed and approved the merge.

Problem-Solving

Problem-solving involved:

• Using console logs and the debugger to isolate problems and determine solutions.
• Using our own Github issue queue to identify and isolate problems for all of us to investigate when convenient.
• Git commits after successful resolution of problems.
• When we were unable to solve a problem after collaboration and more than a half hour of effort, we opened an issue in the General Assembly project queue.

User Stories

USER:

• As an unregistered user, I want to sign up with an email and password.
• As a registered user, I want to sign in with my email and password.
• As a registered user, I want to change my password to a new password.
• As a registered user, I want to sign out.
• As a registered user, I want to be able to view and download all files on the server.
• As a registered user, I want to see the date and time that a file was created/modified.

OWNER:

• As an owner, I want to upload a file.
• As an owner, I want to update my files.
• As an owner, I want to delete my files.
• As an owner, I want to create folders for my files.
• As an owner, I want to update a folder.
• As an owner, I want to delete a folder.
• As an owner, I want to be able to assign tags to my files.

Wireframes