A deployable web platform for collaborative conversation, ideation & sense-making. Use it for free at https://github.com/metamaps/metamaps
Go to file
2018-03-07 21:16:03 -05:00
public user editing in jsx 2018-03-05 23:27:38 -05:00
realtime include realtime server as part of express server 2018-03-04 19:30:17 -05:00
sass user editing in jsx 2018-03-05 23:27:38 -05:00
src convert a tags to link tags in mobile menu 2018-03-07 21:16:03 -05:00
test remove stuff 2018-02-15 13:47:28 -05:00
test_support remove stuff 2018-02-15 13:47:28 -05:00
views notifications 2018-03-07 15:35:27 -05:00
.agignore Into master: two finger pan/zoom, map and topic follows (for internal testing) on the UI, map activity emails (#1084) 2017-03-06 22:49:46 -05:00
.babelrc babel-plugin-lodash to slim down bundle size by 300 KB 2016-09-25 21:53:26 +08:00
.buildpacks multi-buildpack setup for heroku: 2016-08-09 13:49:38 +08:00
.codeclimate.yml re-enable codeclimate duplication 2017-03-10 08:30:01 -08:00
.eslintignore [WIP] code climate config file (#654) 2016-09-23 18:36:47 +08:00
.example-env database called metamaps, not metamap002 in example 2017-01-18 13:10:09 -05:00
.gitignore use node-sass now 2018-03-03 15:57:02 -05:00
.nvmrc add nvmrc 2016-09-10 20:30:58 -04:00
apiProxyMiddleware.js user editing in jsx 2018-03-05 23:27:38 -05:00
Metamaps.ServerData.js.erb remove stuff 2018-02-15 13:47:28 -05:00
package-lock.json list notifications 2018-03-06 07:08:25 -05:00
package.json list notifications 2018-03-06 07:08:25 -05:00
README.md notifications 2018-03-07 15:35:27 -05:00
server.js user editing in jsx 2018-03-05 23:27:38 -05:00
webpack.config.js add express server 2018-02-15 14:16:54 -05:00
webpack.test.config.js new react tests with enzyme library (#1116) 2017-05-13 13:50:52 -04:00

Make sure you have nodemon and node-sass installed $ npm install -g nodemon node-sass

Run the following at the same time, in two terminals

$ API=http://localhost:3001 nodemon server.js
$ node-sass -w sass/application.scss public/css/application.css

To run the server as a daemon that will be re-run if it crashes, you can use the forever node package.

$ npm install -g forever
$ forever start server.js

Run the metamaps api in another terminal using $ rails s -p 3001

Checklist

  • Get the Import lightbox working, and not conflicting on screen
  • Handling CSRF
  • Fix images referenced in the JS
  • Figure out how authentication of requests from the frontend to the API works
  • Figure out how to combine the nodejs realtime server into server.js
  • Notifications: make sure loading states are working for popup and page
  • Notifications: make sure notifications either look nice, or redirect
  • Notifications: pagination
  • Get actioncable working
  • Request unreadNotificationCount
  • Request invite code
  • Request user object itself
  • Handle CSS metacode colors
  • Fix Request An Invite page
  • Make 'new map' action work
  • Modify the remaining rails templates into JSX templates
    • notifications list
    • notification page
    • list metacodes
    • new metacode
    • edit metacode
    • list metacode_sets
    • new metacode set
    • edit metacode set
    • authorized apps
    • registered apps
    • authorize
    • user passwords
  • Modify the RubyOnRails app to only serve JSON responses, no HTML pages anymore
  • Modify the RubyOnRails app to include an endpoint that responds with basic data the front end needs to display (such as the invite code for the user, and the current metamaps build) (a bunch of the data found here: https://github.com/metamaps/metamaps/blob/frontendonly/Metamaps.ServerData.js.erb)
  • Modify the frontend to request that data from the API which is necessary at first to load the page
  • Load the metacodes
  • Load the metacode sets