# Self-Hosting Renovate ## Open Source vs Commercial versions Although Renovate is now best known as a "service" via the GitHub App, that service is actually running this same open source project, so you can get the same functionality if running it yourself. The version you see here in this repository can be cloned or `npm` installed in seconds and give you the same core functionality as in the app. The main feature that's missing is the responsiveness that comes from the app's use of a webhook listener (something not possible in a CLI tool). ## Installing Renovate OSS #### npmjs ``` $ npm install -g renovate ``` #### Docker Renovate is available for Docker via an automated build [renovate/renovate](https://hub.docker.com/r/renovate/renovate/). It builds `latest` based on the `master` branch and all semver tags are published too. All the following are valid: ``` $ docker run --rm renovate/renovate $ docker run --rm renovate/renovate:13.1.1 $ docker run --rm renovate/renovate:13.1 $ docker run --rm renovate/renovate:13 ``` (Please look up what the latest actual tags are though, do not use the above literally). If you wish to configure Renovate using a `config.js` file then map it to `/usr/src/app/config.js` using Docker volumes. For example: ``` $ docker run --rm -v "/path/to/your/config.js:/usr/src/app/config.js" renovate/renovate ``` #### Kubernetes Renovate's official Docker image is compatible with Kubernetes. The following is an example manifest of running Renovate against a GitHub Enterprise server. First the Kubernetes manifest: ```yaml apiVersion: batch/v1beta1 kind: CronJob metadata: name: renovate spec: schedule: '@hourly' concurrencyPolicy: Forbid jobTemplate: spec: template: spec: containers: - name: renovate # Update this to the latest available and then enable Renovate on the manifest image: renovate/renovate:13.153.0 # Environment Variables env: - name: RENOVATE_PLATFORM valueFrom: secretKeyRef: key: renovate-platform name: renovate-env - name: RENOVATE_ENDPOINT valueFrom: secretKeyRef: key: renovate-endpoint name: renovate-env - name: RENOVATE_TOKEN valueFrom: secretKeyRef: key: renovate-token name: renovate-env - name: GITHUB_COM_TOKEN valueFrom: secretKeyRef: key: github-token name: renovate-env - name: RENOVATE_AUTODISCOVER valueFrom: secretKeyRef: key: renovate-autodiscover name: renovate-env restartPolicy: Never ``` And also this accompanying `secret.yaml`: ```yaml apiVersion: v1 kind: Secret metadata: name: renovate-env type: Opaque stringData: renovate-platform: 'github' renovate-endpoint: 'https://github.company.com/api/v3' renovate-token: 'your-github-enterprise-renovate-user-token' github-token: 'any-personal-user-token-for-github-com-for-fetching-changelogs' renovate-autodiscover: 'true' ``` ## Authentication You need to select a user account for `renovate` to assume the identity of, and generate a Personal Access Token. It is recommended to be `@renovate-bot` if you are using a self-hosted server and can pick any username you want. It is also recommended that you configure `config.gitAuthor` with the same identity as your Renovate user, e.g. like `"gitAuthor": "Renovate Bot "`. #### GitHub Enterprise First, [create a personal access token](https://help.github.com/articles/creating-an-access-token-for-command-line-use/) for the bot account (select "repo" permissions). Configure it either as `token` in your `config.js` file, or in environment variable `RENOVATE_TOKEN`, or via CLI `--token=`. #### GitLab CE/EE First, [create a personal access token](https://docs.gitlab.com/ee/api/README.html#personal-access-tokens) for the bot account (select "api" scope). Configure it either as `token` in your `config.js` file, or in environment variable `RENOVATE_TOKEN`, or via CLI `--token=`. Don't forget to configure `platform=gitlab` somewhere in config. #### Bitbucket Cloud First, [create an AppPassword](https://confluence.atlassian.com/bitbucket/app-passwords-828781300.html) for the bot account. Configure it as `password` in your `config.js` file, or in environment variable `RENOVATE_PASSWORD`, or via CLI `--password=`. Also be sure to configure the `username` for your bot account too. Don't forget to configure `platform=bitbucket` somewhere in config. #### Bitbucket Server Create a [Personal Access Token](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html) for your bot account. Configure it as `password` in your `config.js` file, or in environment variable `RENOVATE_PASSWORD`, or via CLI `--password=`. Also configure the `username` for your bot account too, if you decided not to name it `@renovate-bot`. Don't forget to configure `platform=bitbucket-server` somewhere in config. #### Azure DevOps First, [create a personal access token](https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/pats) for the bot account. Configure it either as `token` in your `config.js` file, or in environment variable `RENOVATE_TOKEN`, or via CLI `--token=`. Don't forget to configure `platform=azure` somewhere in config. ## GitHub.com token for release notes If you are running on any platform except github.com, it's important to also configure `GITHUB_COM_TOKEN` containing a personal access token for github.com. This account can actually be _any_ account on GitHub, and needs only read-only access. It's used when fetching release notes for repositories in order to increase the hourly API limit. ## File/directory usage By default, Renovate will store all files within a `renovate/` subdirectory of the operating system's temporary directory, e.g. `/tmp/renovate/`. Repository data will be copied or cloned into unique subdirectories under `repos/`, e.g. `/tmp/renovate/repos/github/owner1/repo-a/`. Cache data - such as Renovate's own cache as well as that for npm, yarn, composer, etc - will be stored in `/tmp/renovate/cache`. If you wish to override the base directory to be used (e.g. instead of `/tmp/renovate/`) then configure a value for `baseDir` in `config.js`, or via env (`RENOVATE_BASE_DIR`) or via CLI (`--base-dir=`). If you wish to override the cache location specifically then configure a value for `cacheDir` instead. ### Identification and Authorization It's possible to sign git commits, but for this you need to set up the GPG key and setting out of band. In short: - Make sure the private key is added via GPG - Tell git about the private key (e.g. `git config --global user.signingkey AABBCCDDEEFF`) - Configure git to sign all commits (`git config --global commit.gpgsign true`) ## Usage The following example uses the Renovate CLI tool, which can be installed by running `npm i -g renovate`. If running your own Renovate bot then you will need a user account that Renovate will run as. It's recommended to use a dedicated account for the bot, e.g. name it `renovate-bot` if on your own instance. Create and save a Personal Access Token for this account. Create a Renovate config file, e.g. here is an example: ```js module.exports = { endpoint: 'https://self-hosted.gitlab/api/v4/', token: '**gitlab_token**', platform: 'gitlab', logFileLevel: 'warn', logLevel: 'info', logFile: '/home/user/renovate.log', onboarding: true, onboardingConfig: { extends: ['config:base'], }, repositories: ['username/repo', 'orgname/repo'], }; ``` Here change the `logFile` and `repositories` to something appropriate. Also replace gitlab-token value with the one created during the previous step. If running against GitHub Enterprise, change the above gitlab values to the equivalent github ones. You can save this file as anything you want and then use `RENOVATE_CONFIG_FILE` env variable to tell Renovate where to find it. Most people will run Renovate via cron, e.g. once per hour. Here is an example bash script that you can point `cron` to: ```sh #!/bin/bash export PATH="/home/user/.yarn/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH" export RENOVATE_CONFIG_FILE="/home/user/renovate-config.js" export RENOVATE_TOKEN="**some-token**" # GitHub, GitLab, Azure DevOps export GITHUB_COM_TOKEN="**github-token**" # Delete this if using github.com # Renovate renovate ``` Note: the GitHub.com token in env is necessary in order to retrieve Release Notes that are usually hosted on github.com. You don't need to add it if you are already running the bot against github.com, but you do need to add it if you're using GitHub Enterprise, GitLab, Azure DevOps, or Bitbucket. You should save and test out this script manually first, and add it to cron once you've verified it. ## Kubernetes for Gitlab, using Git over SSH This section describes how to use git binary with ssh for Gitlab, to avoid API shortcomings. You need to first create a ssh key, then add the public part to Gitlab (see this [guide](https://docs.gitlab.com/ee/ssh/)) Then, you need to create the secret to add the ssh key, and the following config to your container ``` host gitlab.com HostName gitlab.com StrictHostKeyChecking no IdentityFile ~/.ssh/id_rsa User git ``` To easily create the secret, you can do the following (see [docs](https://kubernetes.io/docs/concepts/configuration/secret/#use-case-pod-with-ssh-keys)) ``` kubectl create secret generic ssh-key-secret --from-file=config=/path/to/config --from-file=id_rsa=/path/to/.ssh/id_rsa --from-file=id_rsa.pub=/path/to/.ssh/id_rsa.pub ``` It creates something like this ``` apiVersion: v1 data: config: aG9zdCBnaXRsYWIuY29tCiAgSG9zdE5hbWUgZ2l0bGFiLmNvbQogIFN0cmljdEhvc3RLZXlDaGVja2luZyBubwogIElkZW50aXR5RmlsZSB+Ly5zc2gvaWRfcnNhCiAgVXNlciBnaXQ= id_rsa: id_rsa.pub: kind: Secret metadata: name: ssh-key-secret namespace: ``` Then you just need to add Git author, and mount volumes The final configuration should look like something like this : ``` --- apiVersion: v1 kind: Namespace metadata: name: --- apiVersion: v1 kind: Secret metadata: name: renovate-env namespace: type: Opaque stringData: renovate-platform: 'gitlab' renovate-endpoint: 'https://gitlab.com/api/v4' renovate-token: github-token: renovate-autodiscover: 'false' --- apiVersion: v1 data: config: aG9zdCBnaXRsYWIuY29tCiAgSG9zdE5hbWUgZ2l0bGFiLmNvbQogIFN0cmljdEhvc3RLZXlDaGVja2luZyBubwogIElkZW50aXR5RmlsZSB+Ly5zc2gvaWRfcnNhCiAgVXNlciBnaXQ= id_rsa: id_rsa.pub: kind: Secret metadata: name: ssh-key-secret namespace: --- apiVersion: batch/v1beta1 kind: CronJob metadata: name: renovate namespace: spec: schedule: '@hourly' concurrencyPolicy: Forbid jobTemplate: spec: template: spec: volumes: - name: ssh-key-volume secret: secretName: ssh-key-secret containers: - name: renovate # Update this to the latest available and then enable Renovate on the manifest image: renovate/renovate:14.1.0 volumeMounts: - name: ssh-key-volume readOnly: true mountPath: "/home/ubuntu/.ssh" args: - # Environment Variables env: - name: RENOVATE_GIT_AUTHOR value: '> - name: RENOVATE_GIT_FS value: ssh - name: RENOVATE_PLATFORM valueFrom: secretKeyRef: key: renovate-platform name: renovate-env - name: RENOVATE_ENDPOINT valueFrom: secretKeyRef: key: renovate-endpoint name: renovate-env - name: RENOVATE_TOKEN valueFrom: secretKeyRef: key: renovate-token name: renovate-env - name: GITHUB_COM_TOKEN valueFrom: secretKeyRef: key: github-token name: renovate-env - name: RENOVATE_AUTODISCOVER valueFrom: secretKeyRef: key: renovate-autodiscover name: renovate-env restartPolicy: Never ```