This is the source code for the new Apigility Admin User Interface. We rewrote from scratch the UI in AngularJS with performance improvement and usability.
We added some new features:
- Doctrine support for DB connected REST service;
- DB autodiscovering for table and fields;
- Build package API file, ready for deployment (develop in progress, see TODO list);
- Per-API authentication (develop in progress, see TODO list);
Note
To be able to run the new UI you need to use the develop branch of zf-apigility-skeleton For instance, you can install the develop branch using composer:
composer create-project zfcampus/zf-apigility-skeleton apigility dev-developThis command install the zf-apigility-skeleton application in the apigility local folder.
- npm, for installing the various development requirements, which primarily includes Grunt and Bower, and tools these to utilize.
- Grunt must be installed globally in order to allow using it to serve a source build and run tests.
- Bower must be installed globally in order to allow using it to install development dependencies.
Run the following command from this directory to install dependencies:
npm installIf you have not yet installed Grunt, please do so:
sudo npm install -g gruntIf you have not yet installed Bower, please do so:
sudo npm install -g bowerFinally, invoke Bower to install the relevant CSS and JS libraries:
bower installOnce dependencies are installed, you may run tests using:
grunt testAlternately, fire up a terminal and run:
grunt watchto run tests automatically as files are changed.
There are three ways to invoke the Admin UI: as part of an Apigility project, standalone via node, or via source using grunt.
Add the admin as a dev requirement to your project:
$ composer require-dev "zfcampus/zf-apigility-admin-ui:~1.0"and add the module ZF\Apigility\Admin\Ui to the list of modules in
config/development.config.php.dist (and potentially
config/development.config.php if already in development mode.
Navigating to the URI /apigility/ui in your Apigility application will now hit the UI.
The standalone method fires up a webserver using node. This method requires that
you have a running Apigility Admin API and know the URL, and that that server is
configured to enable CORS; see the Apigility CORS
documentation
if you need help setting this aspect up. Make a note of the URI for your server;
the API URI will be <server>/apigility/api.
Additionally, we recommend noting the URI to your API documentation, so that the navigation item can point to it.
Fire up the admin UI using:
$ node index.js --src --api=<URI to Apigility Admin API (ends in /apigility/api)>(For help with options, see node index.js -h.)
By default, if you do not specify a port, the server will run on port 3000; you
can specify a port with the --port=<port> option.
The grunt serve command does several things:
- Runs
grunt watch, which looks for file changes and runs tasks such as jshint, unit tests, and combining partials into JS templates. - Runs a livereload, static HTTP server; any file change will force it to reload, and trigger any browser windows with the UI loaded to reload.
The grunt server runs in the same way as the standalone server: it accepts the same options, and has the same CORS limitations. As an example:
$ grunt serve --api=<URI to Apigility Admin API (ends in /apigility/api)> \
> --doc=<URI to API documentation> --port=3001 --host=ag.devTo develop the Admin UI (e.g., to add features or fix a bug), you will need to
run the server using the source, not distribution, files. This means using
grunt serve to develop.
All changes to the admin UI code should be made in the src/ directory.
Once you are happy with the changes you have made, you will need to rebuild the distribution files. Run the following from this directory:
$ grunt clean && grunt buildTest that everything is working against the distribution on completion.
If you need to add any new JS or CSS dependencies, please do so as follows:
- Edit the
bower.jsonfile and add the dependency. - Execute
bower install. - Add the files to
src/index.htmlin the appropriate section of the file. - Commit your changes.