A Microservice for URL shortening and sharing.
TODO: Replace with introduction
TODO: Description of features
The application can be run locally or in a docker container, the requirements for each setup are listed below.
A running instance of EGO is required to generate the Authorization tokens and to provide the verification key.
EGO can be cloned and run locally if no public server is available.
Make sure the JWT Verification Key URL is configured, then you can run the server in a docker container or on your local machine.
Update application.yml. Set auth.jwt.publicKeyUrl to the URL to fetch the JWT verification key. The application will not start if it can't set the verification key for the JWTConverter.
The default value in the application.yml file is set to connect to EGO running locally on its default port 8081.
Database migrations and versioning is managed by flyway.
Get current version information:
./flyway -configFiles=<path_to_riff>/riff/src/main/resources/flyway/conf/flyway.conf -locations=filesystem:<path_to_ego>/ego/src/main/resources/flyway/sql info
Run outstanding migrations:
./flyway -configFiles=<path_to_riff>/riff/src/main/resources/flyway/conf/flyway.conf -locations=filesystem:<path_to_ego>/ego/src/main/resources/flyway/sql migrate
To see the migration naming convention, click here.
$ mvn spring-boot:run
Application will run by default on port 1234
Configure the port by changing server.port in application.yml
First build the image:
$ docker-compose build
When ready, run it:
$ docker-compose up
Application will run by default on port 1234
Configure the port by changing services.api.ports in docker-compose.yml. Port 1234 was used by default so the value is easy to identify and change in the configuration file.
TODO: Additional instructions for testing the application.
TODO: API Reference with examples, or a link to a wiki or other documentation source.
TODO: Show folks some love.
Content type
Image
Digest
Size
181.7 MB
Last updated
about 8 years ago
docker pull overture/riff