dryazanov / mockenger

Mockenger - mock-server for developers

Releases

Version 3.0 released

All releases

For users

• Install and run MongoDB
• Download runable jar
• Create configuration file (example)
• Run!

java -jar mockenger-vX.X.jar --spring.config.location=/path/to/your/config/user.properties

Introduction video is available!

For developers

• Install Node JS
• Install Gulp
• Install MongoDB

Run frontend and backend separately

• Start MongoDb

mongod --dbpath /path/to/mongodb/data

Use --auth flag if you created users in your mongodb for access control

mongod --auth --dbpath /path/to/mongodb/data

• Update /core/src/main/resources/application.properties
• Run java backend with maven

cd mockenger/
mvn clean install -DskipTests
cd standalone/
mvn spring-boot:run

Alternatively you can run backend using generated jar file

cd mockenger/
mvn clean install -DskipTests
java -jar standalone/target/mockenger-vX.X.jar --spring.config.location=/path/to/your/config/application.properties

For the frontend there are three options defined in package.json - build, server, build:and:start:server. Use one of them with npm, for example:

cd frontend/
npm run build:and:start:server

In the file gulpfile.js you can set you own properties for server's host and port

Run frontend and backend together

• Start MongoDb
• Create runable jar and run it

cd mockenger/
mvn clean install -DskipTests -P withFrontend
java -jar standalone/target/mockenger-vX.X.jar --spring.config.location=/path/to/your/config/application.properties

---

API response codes

GET: 200 - Request has succeeded, return object or array of objects in the response body 404 - Resource not found

POST/PUT: 200 - Request has succeeded, return added/updated object in the response body

DELETE: 204 - Request has succeeded, no content in the response body

REQUEST ERROR: 400 - Bad request, data from user is not valid. Error description in the response body

INTERNAL ERROR: 500 - Technical error. Error description in the response body