├── .gitignore
├── README.md
├── bundle.js
├── bundle.js.map
├── img
├── favicon-152.png
└── favicon.ico
├── index.html
├── map.geojson
├── params.json
├── select.css
└── web_client
├── App.js
├── Controller.js
├── Entry.js
├── NewEntryForm.js
├── package.json
└── webpack.config.js
/.gitignore:
--------------------------------------------------------------------------------
1 | ### Example user template template
2 | ### Example user template
3 |
4 | # IntelliJ project files
5 | .idea
6 | out
7 | gen
8 | # Created by .ignore support plugin (hsz.mobi)
9 | web_client/node_modules
10 | web_client/build
11 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # [GitMap Demo](https://idoco.github.io/GitMap/)
2 | **A location based job board powered only by GitHub.**
3 |
4 | This demo explores the possibility of building a "serverless" location based app by using only [GitHub's cool ability to render GeoJSON files](https://help.github.com/articles/mapping-geojson-files-on-github/) as interactive maps, and the powerful GitHub API (Nicely wrapped by [Github.js](https://github.com/michael/github)).
5 |
6 | The map view is rendered by GitHub from a [GeoJSON file](map.geojson) stored on GitHub pages and new entries are added to it by forking and creating a pull request on behalf of the submitting user. This GitHub "serverless" architecture is powered by using GitHub itself as the app's database and writing to it by using GitHub's API directly from the user's browser.
7 |
8 | 
9 |
10 | #### How GitMap Works?
11 | - The static site is served by GitHub pages.
12 | - The main page loads a `render.githubusercontent` iframe which renders the [map.geojson](map.geojson) as a full screen map.
13 | - When publishing a new entry, your browser will execute the calls to GitHub API by using [Github.js](https://github.com/michael/github)
14 | - A request will be sent by you to fork this repository.
15 | - The [map.geojson](map.geojson) file in the forked repository will be edited to contain the new published data.
16 | - A pull request will be created on your behalf, to merge the new data to the main repository.
17 | - Your pull request will be manually approved and merged, and the new data will show up on the map after a few moments.
18 |
19 | #### GitHub Authentication
20 | [GitHub OAuth](https://developer.github.com/v3/oauth/) requires that a secret client key will be used to convert the GitHub user login code to the authorization token. Since it is considered unsafe to expose this key, instead of storing it in the webapp I had set up a small [hook.io](https://hook.io/) hook to do the conversion using the secret key. Because this architecture is very irregular I am not sure that [the impact of exposing the client secret](http://tools.ietf.org/html/rfc6819#section-4.1.1) fully apply to it, so I will reconsider this in the future.
21 |
22 | #### Why is [map.geojson](https://github.com/idoco/GitMap/blob/gh-pages/map.geojson?short_path=5406685) filed with empty entries?
23 | This was a very simple trick to avoid merge conflicts issues. Every user adds his new entry in a random line in the file, which makes the chances of two users editing the same line simultaneously very slim. (The probability might still be higher than what you would expect as in the similar case of the [Birthday problem](https://en.wikipedia.org/wiki/Birthday_problem))
24 |
25 | #### My first project with react
26 | 
27 |
28 |
--------------------------------------------------------------------------------
/img/favicon-152.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/idoco/GitMap/a4e665a10f0f76fc6c10b63bfb9ad5570b470b73/img/favicon-152.png
--------------------------------------------------------------------------------
/img/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/idoco/GitMap/a4e665a10f0f76fc6c10b63bfb9ad5570b470b73/img/favicon.ico
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 | GitMap
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
109 | The map view is rendered by GitHub from a
110 |
112 | GeoJSON file
113 |
114 | stored on GitHub pages and new entries are added to it by forking and creating a pull
115 | request on behalf of the submitting user. This GitHub "serverless" architecture is
116 | powered by using GitHub itself as the app's database and writing to it by using GitHub's
117 | API directly from the user's browser.
118 |