A deployable web platform for collaborative conversation, ideation & sense-making. Use it for free at https://github.com/metamaps/metamaps
Find a file
2018-03-08 18:47:14 -05:00
public move lightboxes into react 2018-03-08 07:26:04 -05:00
realtime include realtime server as part of express server 2018-03-04 19:30:17 -05:00
sass newsynapse newtopic and allow/decline access 2018-03-08 09:46:05 -05:00
src cleanup unused 2018-03-08 18:35:47 -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 cleanup unused 2018-03-08 18:35:47 -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 bump node version in nvmrc 2018-03-08 18:47:14 -05: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 explain things better in the README 2018-03-08 18:45:22 -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're running a good up to date LTS version of node, like 8.9.4

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

Run the following at the same time, in TWO SEPARATE terminals. We tell the server where the backend process is running with the API environment variable JS files, and CSS will rebuild automatically, just refresh the page If coding the server itself, you will have to use nodemon, or kill and restart the server process manually

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

To make sure the css files get built, use the following in another terminal

touch sass/application.scss

Run the metamaps api in another terminal using (on port 3001, so the UI can talk to it) For now, make sure you are running on the add-user-route branch of Metamaps, and that it's up to date with the latest on that branch $ rails s -p 3001

open up http://localhost:3000 and start coding!

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

  • Request unreadNotificationCount

  • Request invite code

  • Request user object itself

  • Load the metacodes

  • move ImportDialog lightbox into main app

  • create topic form

  • Fork map lightbox / component

  • fix other places where metacode sets are used

  • make newtopic form load metacodes from users selected ones

  • create synapse form

  • replace old loader with react loader

  • ensure exports of maps work

  • Notifications: make sure notifications either look nice, or redirect

  • Notifications: pagination

  • Get actioncable working

  • lightboxes

  • About lightbox

  • Switch Metacodes lightbox / component

  • break up index.html into parts

  • 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 frontend to request that data from the API which is necessary at first to load the page

    • Load the metacode sets

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