This is an example of using featureflow in an Angular 1 Java jHipster Application
See below for jHipster documents: yarn install yarn global add gulp-cli ./mvnw gulp
We demonstrate here how we use featureflow in the javascript client and on the server side to securely toggle a feature.
Client Side:
- We import featureflow in the bower.json
"featureflow-ng": "1.3.3",
- 'gulp build' calls gulp-inject to add the featureflow-ng js file to the index.html
<script src="bower_components/featureflow-ng/featureflow-ng.js"></script>
- We register it in app.module
angular .module('featureflowExampleAngularOneJavaApp', [ ... 'ng-featureflow' ]) .run(run);
- Configure it in app.module.js config method. This will ensure we have an initial set of featureflow controls.
To set it up for your project copy your 'JS Client Environment SDK Key' into the variable FF_API_KEY below:
angular .module('featureflowExampleAngularOneJavaApp') .config(['featureflowProvider', function(featureflowProvider){ var FF_API_KEY = 'js-env-mykey1234567890'; featureflowProvider.init(FF_API_KEY, {}); }]);
- We inject featureflow into the navbar.controller.js
function NavbarController (... featureflow) { ...
- and expose it to our navbar.controller scope
vm.featureflow = featureflow;
- then evaluate directly in the navbar.html.
<li ng-if="vm.featureflow.evaluate('entity-menu').is('on')" ng-class="{active: vm.$state.includes('entity')}" ng-switch-when="true" uib-dropdown class="dropdown pointer">
- When the user logs in we reevaluate the context to get user-specific values - in auth.service.js authThen:
var user = { key: Principal, attributes: { admin: $rootScope.account.isAdmin, name: acc.firstName + " " + acc.lastName, company: acc.company, email: acc.emails, state: acc.state } }; featureflow.updateUser(user);
This application was generated using JHipster 4.5.5, you can find documentation and help at https://jhipster.github.io/documentation-archive/v4.5.5.
Before you can build this project, you must install and configure the following dependencies on your machine:
- Node.js: We use Node to run a development web server and build the project. Depending on your system, you can install Node either from source or as a pre-packaged bundle.
- Yarn: We use Yarn to manage Node dependencies. Depending on your system, you can install Yarn either from source or as a pre-packaged bundle.
After installing Node, you should be able to run the following command to install development tools. You will only need to run this command when dependencies change in package.json.
yarn install
We use Gulp as our build system. Install the Gulp command-line tool globally with:
yarn global add gulp-cli
Run the following commands in two separate terminals to create a blissful development experience where your browser auto-refreshes when files change on your hard drive.
./mvnw
gulp
Bower is used to manage CSS and JavaScript dependencies used in this application. You can upgrade dependencies by
specifying a newer version in bower.json. You can also run bower update
and bower install
to manage dependencies.
Add the -h
flag on any command to see how you can use it. For example, bower update -h
.
For further instructions on how to develop with JHipster, have a look at Using JHipster in development.
To optimize the FeatureflowExampleAngularOneJava application for production, run:
./mvnw -Pprod clean package
This will concatenate and minify the client CSS and JavaScript files. It will also modify index.html
so it references these new files.
To ensure everything worked, run:
java -jar target/*.war
Then navigate to http://localhost:8080 in your browser.
Refer to Using JHipster in production for more details.
To launch your application's tests, run:
./mvnw clean test
Unit tests are run by Karma and written with Jasmine. They're located in src/test/javascript/ and can be run with:
gulp test
For more information, refer to the Running tests page.
You can use Docker to improve your JHipster development experience. A number of docker-compose configuration are available in the src/main/docker folder to launch required third party services. For example, to start a mysql database in a docker container, run:
docker-compose -f src/main/docker/mysql.yml up -d
To stop it and remove the container, run:
docker-compose -f src/main/docker/mysql.yml down
You can also fully dockerize your application and all the services that it depends on. To achieve this, first build a docker image of your app by running:
./mvnw package -Pprod docker:build
Then run:
docker-compose -f src/main/docker/app.yml up -d
For more information refer to Using Docker and Docker-Compose, this page also contains information on the docker-compose sub-generator (jhipster docker-compose
), which is able to generate docker configurations for one or several JHipster applications.
To configure CI for your project, run the ci-cd sub-generator (jhipster ci-cd
), this will let you generate configuration files for a number of Continuous Integration systems. Consult the Setting up Continuous Integration page for more information.