When you’re walking around the city, you want to enjoy the fun and interesting things and avoid the dangerous / gross stuff. Amblr lets you share points of interest with other users and lets you see what other have added. It’s kind of like Waze, but for walkers.
[Bryan Newby - Developer] (https://github.com/brnewby602)
Table of Contents
When you load the app, you'll see a Google Map where you can add a point of interest (POI) at your current location by clicking a menu link or at any location by touching and holding on the map for 1 second. After adding a POI, you can add details and save it to the database. Touch existing POIs to see the details.
Sign In and Sign Out features are implemented with Passport.js, but they do not restrict user functions yet.
- MongoDB 2.1.16
- Express 4.13.4
- Angular 1.4.3 with Ionic 1.2.4
- Node 4.4.2
- Google Maps API
NPM Modules and Bower Components
For complete details, see package.json files in Server and Client folders, and bower.json in Client folder.
In case you're curious about the mobile technologies:
Ionic - A mobile development framework for Angular.js - see the [official site] (http://ionicframework.com/) and [this blog post] (http://blog.ionic.io/where-does-the-ionic-framework-fit-in/)
See the [file structure] (https://github.com/mediocreokra/amblr/blob/master/_FILE-STRUCTURE.MD) for a guide to what's included.
Server logging will be done both in the console and to /server/logs/log.log. Log level can be configured in /server/config/logger.js
From within the
npm install bower install
From within the
npm install grunt server-dev
The application is configured to use https only due to the use of getCurrentLocation and Chrome not allowing non-secure requests for this any longer. To create a self-signed certificate, perform the following commands in server/config/keys directory:
openssl req -newkey rsa:2048 -new -nodes -keyout key.pem -out csr.pem openssl x509 -req -days 365 -in csr.pem -signkey key.pem -out server.crt
1. After starting mongod and then the server, go to https://localhost:4443. 2. Click on the lock icon that should have a red X in the location bar. 3. Click the Details link in the popup that appears 4. Click the View Certificate button that is displayed in the Security tab of Chrome Dev Tools (this should open automatically after clickig Details) 5. A popup appears with the certificate information. Drag the icon of the certificate to your desktop. This will create the .cer file on your desktop. 6. Double click the .cer file and on the popup, change the Keychain dropdown to: System and click Add. 7. Enter your password and click Modify Keychain 8. Hit URL again. 9. Go to the Advanced link on the error 10. Click the Proceed to localhost (unsafe) linkto fiew 11. You should now be able view the site over HTTPS now!
View the current issues list here
See CONTRIBUTING.md for contribution guidelines.