https://github.com/arranbartish/identity
Centralized Identity Application
https://github.com/arranbartish/identity
Last synced: 9 months ago
JSON representation
Centralized Identity Application
- Host: GitHub
- URL: https://github.com/arranbartish/identity
- Owner: arranbartish
- License: mit
- Created: 2016-06-15T21:13:12.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2017-02-01T22:37:54.000Z (over 9 years ago)
- Last Synced: 2025-02-23T21:27:45.221Z (over 1 year ago)
- Language: Java
- Size: 1.09 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Wasted time app
An app for tracking wasted time. I've stayed pretty close to the ideals of a 12 factor app.
## dev url
https://arran-wasted-time.herokuapp.com
## Improvements / limitations
- Dockerize the artifact so that testing and deployment use the same artifact
- not implemented openID or crowd integration
# Install notes
## As a deployable jar ( Prefered )
1. user@host:~/source-root$ mvn clean package
2. user@host:~/source-root$ java -Dserver.port=(DESIRED_PORT) -jar wasted-app/target/wasted-app-(VERSION).jar
The application should now be deployed locally on the port you defined in the above command.
# About the Project
This is a Spring boot app that is continuously deployed to heroku on the URL described in the [POM](parent/pom.xml)
## Continuous Deployment
The project is build practicing continuous delivery from the beginning and is described in the [DSL](pipeline-dsl.groovy)
Git flow is being used to allow feature branches to be automatically integrated to the develop branch the moment they pass. Obviously the means tests must be provided before pushing to origin. Just to be extra clear... TEST FIRST
All changes wait on the develop branch until it is decided to cut a candidate branch. The Candidate will result in a versioned release which will be tested, followed by a migration to master and heroku
The command to start the app on heroku is in the Procfile and can be updated any time by changing the [Heroku Procfile template](HerokuProcfile.template). Currently there is only built in support for the version placeholder
### Testing
Tests are all of a unit flavour, however I have made a clear separation between what are true unit tests and those that are integration tests. This separation has been expressed in the maven lifecycle by running all *Test.java files in the test phase and all *IntegrationTest.java files in the integration-test phase.
#### The Jar
The jar is always built and tested by default with no additional effort.
#### The war
The war only builds when the JAR-AND-WAR maven profile is used. The cargo plugin is bound to the pre-integration-test phase and deploys the packaged war for confirming the deployable
## 12 factor app
### I. Codebase
Single code base using gitflow and multiple version.
### II. Dependencies
All dependencies are isolated especially SNAPSHOT intermodule dependencies. This can be see in the way the pipeline is built
### III. Config
The app comes with some configurable defaults, however the keys and environment specific items are configured on heroku
### IV. Backing services
Besides the database the only service being used is appdirect which is being used as a service.
### V. Build, release, run
The pipeline has this at its heart
### VI. Processes
App is stateless except for the spring security session, though this can be swapped out got reddit
### VII. Port binding
Self contained... except of course for the optional war component.
### VIII. Concurrency
Stateless. If the app supported user authentication I would have used redis and not app session
### IX. Disposability
Totally disposable.
### X. Dev/prod parity
The app code deployed locally, used on CI, and on heroku is the same. This could be improved by using docker.
### XI. Logs
Logs have not been used too much in this case.
### XII. Admin processes
No real admin processes.