Moveez
is a service to keep track of the movies you would like to watch in future. It shows you the ratings from sites like iMDB.com and Rottentomatoes.com.
Future updates might include:
- It even alerts you when a movie is running in cinema or is available on a VoD-plattform of your choice.
- Furthermore you can browse your list by ratings, release date or genre.
- an own score calculated by the individual ratings of all moveez-users.
We have switched from Jenkins to Azure DevOps. You can find the workspace here.
Within Azure DevOps we are using Azure Pipelines to build and release moveez. The pipeline configuration is done via azure-pipeline.yml
per service.
We use sonarcloud.io for our static code analysis. It is automaticly triggered for all branches as a parallel step to the build. The results are published to Azure DevOps and a dashboard.
We use prettier.io to lint our code style. To prevent manual effort, you can add the prettier to your .git/hooks
. Just use the following pre-commit
hook (requires prettier to be installed globally via npm):
#!/bin/sh
FILES=$(git diff --cached --name-only --diff-filter=ACM “.js” “.jsx” | sed ‘s| |\\ |g’)
[ -z “$FILES” ] && exit 0
# Prettify all selected files
echo “$FILES” | xargs prettier --write
# Add back the modified/prettified files to staging
echo “$FILES” | xargs git add
exit 0
We use cypress.io to perform our regression testing. It is automaticly triggered for all branches on UAT stage after the deployment. The results are published to Azure DevOps and a dashboard.
This app consists of multiple microservices, all based on Express. Our data is managed by MongoDB - the setup is described in the database directory. To run the services and database we are using Rancher, which setup is described here. The deployment of services to Rancher is done via helm.
- Set up the servers and rancher
- Set up the network configuration including DNS and TLS
- Set up the databases for UAT and PROD
- Set up the secret for the facebook login
To monitor our services we are using uptime robot that can be visited here: https://uptimerobot.com/dashboard#mainDashboard
Currently you have to look at the container logs e. g. via Rancher, but in future we want to use Graylog or something similar.