Skip to content

DataMascara/minimum-movement-demo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 

Repository files navigation

minimum movement catalog

This is a database of dance movements.

Project idea from Maho Ogawa (www.suisoco.com) for her dissertation study at Brooklyn College; web development overseen by Katherine Chuang.

This is a project for CISC 4900 to enhance the features of the minimum movement web app.

Setup

Dependencies


Contribution guide

First - contact (@katychuang) to get permissions.

Setup from this repo

  1. Install CLI tools needed for managing various
    • All at once npm i -g firebase-tools create-react-app
  2. Clone this repository
  3. Create a new branch for your feature work and switch to the newly made branch (All at once) git checkout -b <branch-name>
  4. If you need to update your working directory for whatever reason while inside your branch use git pull
  5. Pushing to "origin" will add your branch to a branch in the main codebase on GitHub, from which you will be able to merge your changes to the main branch (or leave them in the branch in the main codebase without merging)

Install frontend dependencies:

  1. Go into the view subfolder. From the project root, cd view
  2. install dependencies. Running npm i works because there is a package.json file in that subfolder that specifies which libraries to install.

Development flow

To test the UI locally, you must be in the view folder before running npm start - this command looks at the package.json file for configuration information. While you're in that mode, it will refresh the page as you make changes to the JS files. You can set the proxy field in the package.json to connect to a specific backend location. Exit out of that preview mode using CTRL+C to return to a regular terminal prompt. Make sure that you've cleaned up the URLs to the backend if you've been shifting between localhost and prod modes.

To deploy the UI changes, npm run build while in the view folder to use create-react-app's tools for packaging a deployable version. The package.json is configured such that a new build folder is created with the files to deploy in there. Go back to the root folder cd .. to run the Firebase commands for deploying to the hosting server: firebase deploy --only hosting --project <project-id>


Folder Structure of the project

├── .firebaserc
├── firebase.json
└── view                    # frontend code
    ├── build               # created from `npm run build`, deployed folder
    ├── package.json        # for npm
    ├── public              # used in producing build folder
    └── src                 # the whole app
        ├── App.js
        ├── components
        │   ├── lexicon.js
        │   ├── movement.js
        ├── index.js
        └── pages
            └── exhibit.js   # defaults to the landing page
            --- bodytension.js
        |   |--  spatiallevel.js
        |   |--  range.js
        |   |--  mood.js
         

URL Patterns

In the comments of the JS files, you'll see these as the {{base_url}} variable

Firebase Hosting

For frontend

Firebase Storate

For media assets

  • https://storage.googleapis.com/<project-id>/<folder>/<path>/<file>

Credits

References

Helpful Links for frontend dev:


Troubleshooting

  • Multiple NVM versions From: https://www.digitalocean.com/community/tutorials/nodejs-node-version-manager

    Install NVM

    #install Node Version Manger
    `curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`

    Settings

    # set $NVM_DIR
    export NVM_DIR="$HOME/.nvm"
    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"

    Then, set the nvm version you want:

    • To install, nvm install 12
    • To switch node version, nvm use 12

About

minimum-movement-demo.web.app

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published