Not just another todo list app
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
assets Change List Name to Search Bar Aug 12, 2018
cert Fix SSL Terraform Mar 22, 2018
dist Update Checkbox Styles & Task Expanded Styles May 5, 2018
nitro.sdk.test Add Date & List Indicators Back May 17, 2018
nitro.sdk
nitro.ui Fix Archived Draggable Sep 17, 2018
.babelrc
.dockerignore Basic Dockerfile Mar 12, 2018
.eslintrc.js Start Cleaning Up UI API Nov 3, 2017
.flowconfig
.gitignore Fix Production Build May 16, 2018
.npmignore Add more manifest icons & fix login bugs Aug 26, 2017
.prettierrc Notes Indicator Oct 28, 2017
.travis.yml Remove Terraforms Jun 7, 2018
AUTHORS Add Lists Sync Apr 29, 2017
COPYING Change to AGPL Nov 10, 2017
Dockerfile New Dockerfile Stuff Jun 6, 2018
README.md Add More Tests & Start on Magic Lists Nov 4, 2017
config.js
nginx-default.conf New Dockerfile Stuff Jun 6, 2018
package-lock.json UI Changes for Mobile New Task Sep 17, 2018
package.json Update Dependencies & Fix Overdue Showing on Completed Tasks Aug 11, 2018
webpack.config.js

README.md

Nitro 3

Build Status Dependency Status devDependency Status

A brand new rewrite. Check out the Wiki for what's new and happening, or tweet me @consindo.

Build Instructions

  • You will need node.js & npm installed.
  • Then run npm install

Development (without server)

  • Use npm run test:fast to run tests only, without building and coverage.
  • You can use npm run watch. It uses webpack-dev-server, which has nice live js & css reloading.
  • Sign in with local@nitrotasks.com, no password.

Development (with server)

  • Go to https://github.com/nitrotasks/nitro-server to download and use the server.
  • If you're developing the client too, the webpack-dev-server will proxy API requests to localhost:8040/a - you can change this in webpack.config.js.

Production

  • This is published as a npm package, prebuilt with the API route as /a.
  • Nitro Server pulls the package from NPM, and serves the module as the app.

Otherwise

  • Use npm run build to create a production build.
  • Serve this from nitro-server by changing the config.
  • If you're the maintainer, use npm publish and change the wanted package in the nitro-server package.json.