GitXplorerGitXplorer
t

crucible

public
116 stars
20 forks
11 issues

Commits

List of commits on branch master.
Unverified
ad81f694bc5cdef995e51f91ffc5475a24640114

v0.4.1

ttivac committed 8 years ago
Unverified
fe511c42fe3b89c8ed5d56e9e27bc601242291ee

That worked! Removing logging

ttivac committed 8 years ago
Unverified
72f93de36a68c55bf5d2b163701e9dbf6f237cf9

rework blob and more logging

ttivac committed 8 years ago
Unverified
0c59a6659e3758afe342de8a09bdd27885d39ead

Guessing

ttivac committed 8 years ago
Unverified
577c1a3b55c1d933a87de8717779e0e132727625

chore: npm5, shared stylelint config

ttivac committed 8 years ago
Unverified
72213f5a1a3ac270acf88343bfefa11668ae4c77

test: testing an idea

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