Web-based admin UI for the Para backend server
Switch branches/tags
Nothing to show
Clone or download
Latest commit a3adf94 Oct 7, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs fixed #2 Oct 7, 2018
.gitattributes initial commit Mar 23, 2016
.gitignore fixed _.upperFirst missing Mar 24, 2016
CNAME
LICENSE happy new year Jan 2, 2018
README.md fix simple typo Aug 30, 2018

README.md

Logo

Para Web Console

Join the chat at https://gitter.im/Erudika/para

What is this?

Para was designed as a simple and modular backend framework for object persistence and retrieval. It helps you build applications faster by taking care of the backend. It works on three levels - objects are stored in a NoSQL data store or any old relational database, then automatically indexed by a search engine and finally, cached.

This is the basic, open source admin console for managing your own Para backend. There's a much more advanced and feature-rich web UI at ParaIO.com - the hosted Para service.

screenshot

Quick start

You don't have to install anything, just open the web UI and start using it!

Open the Web Console from here: console.paraio.org

NOTE: If you connect to a Para server on http://localhost or other non-https domain, you should do so from http://console.paraio.org. Some browsers don't allow HTTPS pages to make CORS requests to insecure HTTP endpoints.

Run it locally

To run it locally, start up a web server like Express or Python:

$ cd docs && python -m SimpleHTTPServer 9000

OR:

$ npm run server

There's no need to run npm install.

The admin interface is client-side only and your secret key is never sent over the network. Instead, a JWT access token is generated locally and sent to the server on each request.

ng-admin and Restangular

This project is based on ng-admin and Restangular so be sure to check their docs first:

ng-admin docs

Restangular docs

Para documentation

Read the Docs

Contributing

  1. Fork this repository and clone the fork to your machine
  2. Create a branch (git checkout -b my-new-feature)
  3. Implement a new feature or fix a bug and add some tests
  4. Commit your changes (git commit -am 'Added a new feature')
  5. Push the branch to your fork on GitHub (git push origin my-new-feature)
  6. Create new Pull Request from your fork

For more information see CONTRIBUTING.md

License

Apache 2.0