angular-moviemasher | Example deployment of moviemasher.js and moviemasher.rb

It's important to remember this project is just an example deployment and not intended to be a fully functional, user-driven site out of the box. For instance, by default it uses HTTP authentication that accepts any username and password combination - hardly a recommended mechanism! It also stores all data locally in JSON files instead of using a database or other mechanism. Download the latest ZIP and grab the compiled files in the dist folder. An example application is app and if you don't have the required modules installed they are in node_modules.
npm install --save @moviemasher/angular-moviemasher
edit the config/moviemasher.ini file and place outside your web root directory
add its parent directory to PHP's include_path configuration option somehow or edit app/php/include/authutils.php to specify its full path
if file option is 's3' then create the s3 bucket
or if file option is 'local' then change the permissions of the directory specified in the user_media_directory option such that the web server can work with it
if client option is 'sqs' then create the sqs queue, and set sqs_queue_url option in moviemasher.rb configuration
or if client option is 'local' then set queue_directory in moviemasher.rb and change its permissions so the web server can work with it
change the permissions of the directories specified in temporary_directory and user_data_directory such that the web server process can work with them
install the app, bower_components and dist directories somewhere under web root and load index.html in a web browser
Several docker-compose files provide a simple mechanism to update dependencies.
cd config/docker/composer
docker-compose run --rm composer
cd config/docker/node
docker-compose run npm
cd config/docker/node
docker-compose run --rm grunt