final_project_interactive_climbing_gym_map

.env

@@ -0,0 +1,3 @@
+MONGODB_USER=tester
+MONGODB_PASS=tester123
+MONGODB_HOST="cluster0.ulx2a2w.mongodb.net"

README.md

@@ -1,49 +1,29 @@
-# Final Project
-*Due October 13th (final day of the term)*
+#Interactive Climbing Gym Map
+Created by: Travis Thompson + Colby Frechette
 
-For your final project, you'll implement a web application that exhibits understanding of the course materials. 
-This project should provide an opportunity to both be creative and to pursue individual research and learning goals.
+Website Link:
+http://142.93.202.135/
 
-## General description
-Your project should consist of a complete Web application, exhibiting facets of the three main sections of the course material:
+Video Link:
+https://www.youtube.com/watch?v=YD8O8OOUIMM
 
-- Static web page content and design. You should have a project that is accessible, easily navigable, and features significant content.
-- Dynamic behavior implemented with JavaScript (TypeScript is also allowed if your group wants to explore it).
-- Server-side programming *using Node.js*. Typically this will take the form of some sort of persistent data (database), authentication, and possibly server-side computation. 
-- A video (less than five minutes) where each group member explains some aspect of the project. An easy way to produce this video is for you all the groups members to join a Zoom call that is recorded; each member can share their screen when they discuss the project or one member can "drive" the interface while other members narrate (this second option will probably work better.) The video should be posted on YouTube or some other accessible video hosting service. Make sure your video is less than five minutes, but long enough to successfully  explain your project and show it in action. There is no minimum video length.
+For this project, we created an interactive climbing gym map to display where climbs exist in a gym. Currently, most climbing gyms have no indication of where certain grades are located in a gym, leaving a climber to wander around looking for climbs they would like to try. With our program, route setters can add climbs to the database with the admin page, and climbers can easily find the climbs they want to try with a multitude of actions. Hovering over sections  as well as utilizing filters can be used to locate climbs, allowing the user to find the type of climb they would like to try, as well as the grade.
 
-## Project ideation
-Excellent projects typically serve someone/some group; for this assignment you need to define your users and stakeholders. I encourage you to identify projects that will have impact, either artistically, politically, or in terms of productivity. 
+This program is intended for use for Central Rock Gym in Worcester, where we both climb regularly. By combining the different techniques we have learned in class, we have created a robust, visually appealing, and useful program that allows us to see the climbs. In the future, we plan on expanding this project and potentially working with CRG to implement it into their gym ecosystem.
 
-### Deliverables
+There should be no additional information needed, other than a basic knowledge of climbing, which can be found here: https://en.wikipedia.org/wiki/Climbing. 
 
-#### Form Team (due 9/25)
-Students are will work in teams of 3-5 students for the project; teams of two can be approved with the permission of the instructor. Working in teams should help enable you to build a good project in a limited amount of time.  Use the `#project-logistics` channel in Discord to pitch ideas for final projects and/or find fellow team members as needed.
+We used the following technologies:
+- Bootstrap - a CSS framework to make the app visually appealing
+- Node.js - for managing the server
+- d3 - for displaying the map
+- Express - for server management
+- mongoDB - for persistent data storage
 
-Teams must be in place by end of day on Sunday, September 25th. If you have not identified a team at this point, you will be assigned a team. You will be given some class time on Monday to work on your proposal, but please plan on reserving additional time outside of class as needed.
+We faced relatively few challenges (other than time from other class schedules), however some included, hosting the server, sorting data, needing to manually write down all the climbs in the gym (yes, it is accurate to CRG right now, if you have not been, we recommend visting!).
 
-#### Proposal (due 9/27) 
-Provide an outline of your project direction and the names of associated team members. 
-The outline should have enough detail so that staff can determine if it meets the minimum expectations, or if it goes too far to be reasonable by the deadline. Please include a general description of a project, and list of key technologies/libraries you plan on using (e.g. React, Three.js, Svelte, TypeScript etc.). Two to four paragraps should provide enough level of detail. Name the file proposal.md and submit a pull request by Tuesday, September 27th at 11:59 PM (end of day). Only one pull request is required per team.
+Travis - Server hosting, d3 visualization and svg creation, mongoDB setup.
+Colby - HTML base, Javascript logic, and CSS styling, ideation, README.
+Both - we worked together often to help eachother through the struggles we had along the way, and played to our strengths when one of us was not familiar with a technology that the other was.
 
-There are no other scheduled checkpoints for your project. 
-
-#### Turning in Your Project
-Submit a second PR on the final project repo to turn in your app and code. Again, only one pull request per team.
-
-Deploy your app, in the form of a webpage, to Glitch/Heroku/Digital Ocean or some other service; it is critical that the application functions correctly wherever you post it.
-
-The README for your second pull request doesn’t need to be a formal report, but it should contain:
-
-1. A brief description of what you created, and a link to the project itself (two paragraphs of text)
-2. Any additional instructions that might be needed to fully use your project (login information etc.)
-3. An outline of the technologies you used and how you used them.
-4. What challenges you faced in completing the project.
-5. What each group member was responsible for designing / developing.
-6. A link to your project video.
-
-Think of 1,3, and 4 in particular in a similar vein to the design / tech achievements for A1—A4… make a case for why what you did was challenging and why your implementation deserves a grade of 100%.
-
-## FAQs
-
-- **Can I use XYZ framework?** You can use any web-based frameworks or tools available, but for your server programming you need to use Node.js. Your client-side scripting language should be either JavaScript or TypeScript.
+We really enjoyed this project and wish we had more time to work on it and make it better.

bundler/webpack.common.js

@@ -0,0 +1,73 @@
+const CopyWebpackPlugin = require('copy-webpack-plugin')
+const HtmlWebpackPlugin = require('html-webpack-plugin')
+const MiniCSSExtractPlugin = require('mini-css-extract-plugin')
+const path = require('path')
+
+module.exports = {
+    entry: {
+        main: path.resolve(__dirname, '../src/main/script.js'),
+        admin: path.resolve(__dirname, '../src/admin/admin.js')
+    },
+    output:
+    {
+        hashFunction: 'xxhash64',
+        filename: 'bundle.[contenthash].js',
+        path: path.resolve(__dirname, '../public')
+    },
+    devtool: 'source-map',
+    plugins:
+    [
+        new CopyWebpackPlugin({
+            patterns: [
+                { from: path.resolve(__dirname, '../static') }
+            ]
+        }),
+        new HtmlWebpackPlugin({
+            template: path.resolve(__dirname, '../src/main/index.html'),
+            filename: "index.html",
+            chunks: ["main"],
+            minify: true
+        }),
+        new HtmlWebpackPlugin({
+            template: path.resolve(__dirname, '../src/admin/adminPage.html'),
+            filename: "adminPage.html",
+            chunks: ["admin"],
+            minify: true
+        }),
+        new MiniCSSExtractPlugin()
+    ],
+    module:
+    {
+        rules:
+        [
+            // HTML
+            {
+                test: /\.(html)$/,
+                use:
+                [
+                    'html-loader'
+                ]
+            },
+
+            // JS
+            {
+                test: /\.js$/,
+                exclude: /node_modules/,
+                use:
+                [
+                    'babel-loader'
+                ]
+            },
+
+            // CSS
+            {
+                test: /\.css$/,
+                use:
+                [
+                    MiniCSSExtractPlugin.loader,
+                    'css-loader'
+                ]
+            }
+        ]
+    }
+}

bundler/webpack.dev.js

@@ -0,0 +1,49 @@
+const path = require('path')
+const { merge } = require('webpack-merge')
+const commonConfiguration = require('./webpack.common.js')
+const ip = require('internal-ip')
+const portFinderSync = require('portfinder-sync')
+
+const infoColor = (_message) =>
+{
+    return `\u001b[1m\u001b[34m${_message}\u001b[39m\u001b[22m`
+}
+
+module.exports = merge(
+    commonConfiguration,
+    {
+        stats: 'errors-warnings',
+        mode: 'development',
+        devServer:
+        {
+            host: 'local-ip',
+            port: portFinderSync.getPort(8080),
+            open: true,
+            https: false,
+            allowedHosts: 'all',
+            hot: false,
+            watchFiles: ['src/**', 'static/**'],
+            static:
+            {
+                watch: true,
+                directory: path.join(__dirname, '../static')
+            },
+            client:
+            {
+                logging: 'none',
+                overlay: true,
+                progress: false
+            },
+            onAfterSetupMiddleware: function(devServer)
+            {
+                const port = devServer.options.port
+                const https = devServer.options.https ? 's' : ''
+                const localIp = ip.v4.sync()
+                const domain1 = `http${https}://${localIp}:${port}`
+                const domain2 = `http${https}://localhost:${port}`
+
+                console.log(`Project running at:\n  - ${infoColor(domain1)}\n  - ${infoColor(domain2)}`)
+            }
+        }
+    }
+)

bundler/webpack.prod.js

@@ -0,0 +1,14 @@
+const { merge } = require('webpack-merge')
+const commonConfiguration = require('./webpack.common.js')
+const { CleanWebpackPlugin } = require('clean-webpack-plugin')
+
+module.exports = merge(
+    commonConfiguration,
+    {
+        mode: 'production',
+        plugins:
+        [
+            new CleanWebpackPlugin()
+        ]
+    }
+)