https://github.com/txchen/pmev
Poor man's event viewer
https://github.com/txchen/pmev
Last synced: about 2 months ago
JSON representation
Poor man's event viewer
- Host: GitHub
- URL: https://github.com/txchen/pmev
- Owner: txchen
- License: mit
- Created: 2015-02-02T05:52:58.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2015-10-04T16:53:29.000Z (over 10 years ago)
- Last Synced: 2025-04-27T11:02:36.641Z (about 1 year ago)
- Language: CSS
- Size: 352 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# PMEV - Poor man's event viewer
Design for collecting some random personal events, like the ones from NAS.
This is a nodejs app that takes events and shows in html. It uses Parse as the storage layer and it can be hosted on azure.
### How to use
https://mypmev.azurewebsites.net/
To post new event, use basic auth and http POST:
```
http POST https://mypmev.azurewebsites.net/events \
host=myhost message=testing -a API_USER:
```
To use httpie in cronjob, make sure you add the `--ignore-stdin` option:
```
http --ignore-stdin POST https://mypmev.azurewebsites.net/events \
host=myhost message=testing -a API_USER:
```
To view the events, browse the web site and login as google account.
### How to deploy
Firstly, create a google api account, enable google+ and contact API in the console. Create an project, set the callback url and get the API client and API secret.
Then, create a Parse.com account, create a project, get the ParseAPPID and REST API KEY.
Finally, create an azure account, setup azure webapp, hook up with github repository.
Follow `.envSample` to config the variables in azure webapp.
### How to develop
First of all, create an `.env` file with the correct configurations. `.envSample` will show you what should be configured.
The app contains an API backend and a static frontend, to make everything auto reload after changes, run:
```
npm run dev
```
It would launch a webpack-dev-server, listening on http://localhost:18000 and proxy all the not found request to http://localhost:17000. Backend nodejs server will listen on http://localhost:17000. Open http://localhost:18000 in browser and start developing.
Webpack would not write the generated files during dev mode, so after code changes, run:
```
npm run dist
```
It would generated the final bundle javascripts.