GitXplorerGitXplorer
t

crucible

public
116 stars
20 forks
11 issues

Commits

List of commits on branch master.
Unverified
398efecb3a03dd75024817addb1c7524c99c25cc

v0.4.0

ttivac committed 8 years ago
Unverified
f25dea534c3c1aa570e492ebbd9f4af1b506632b

just kidding, replace native dep

ttivac committed 8 years ago
Unverified
80848813a8daaed207a759112ec22309b526e208

feat: inline web worker as a blob

ttivac committed 8 years ago
Unverified
491f11812ef69e07544e1caac82e9ed2c1131419

v0.3.5

ttivac committed 8 years ago
Unverified
c9282309b5640691b255f177749c0b0a34775fba

chore: fix linter error

ttivac committed 8 years ago
Unverified
09d761924b1946caf4509cbde051d0b084db855e

chore: add release script to automate versioning

ttivac committed 8 years ago

README

The README file for this repository.

Crucible

Fully client-side single-page application talking to FireBase to build a customizable CMS backed by a robust RESTful API. (Because the API is just FireBase!)

Installation

  1. npm install crucible
  2. Rename index-example.html to index.html, changing the <base> tag if necessary
  3. Rename config-example.js to config.js and set your firebase endpoint
  4. Open index.html in a browser

Development

  1. Create a fork of https://github.com/tivac/crucible
  2. git clone https://github.com/<username>/crucible.git
  3. cd crucible
  4. npm install
  5. Rename index-example.html to index.html, changing the <base> tag if necessary
  6. Rename config-example.js to config.js and set your firebase endpoint
  7. npm run build
  8. npm start
  9. Open http://localhost:9966 in a browser

Usage

You'll want to create a schema first. Schemas are JSON-ish documents that contain some number of fields.

Once you've created a schema you can create instances of that schema. All edits are synced in near-real-time to FireBase, so your data should always be in sync.

Schema Documentation