Selfhosted

38707 readers

677 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

824

I love my Gitea. Any tips and tricks? (sh.itjust.works)

submitted 8 months ago by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 8 months ago (1 children)

Absolutely!

Running local, self hosted forgejo with a few runners.

Now my code is neatly checked with pre-commit and linters, build when new tags are pushed, renovate is scheduled every 24 hours to check for new releases of stuff etc.

Just a few containers and a happy user :-)

[–] [email protected] 3 points 8 months ago (2 children)

do you use forgejo-runner or another ci/cd image?

[–] [email protected] 2 points 8 months ago

I am not the OP but I use Woodpecker CI.

I like to keep things separated, in a KISS fashion. This makes changing either software easier.

[–] [email protected] 2 points 8 months ago

Still testing and fiddling, but I'm using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:

on:
  schedule:
    - cron: '5 2 * * *'
    - cron: '5 14 * * *'

jobs:
  build:
    runs-on: docker
    container:
      image: renovate/renovate:37.140-full
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Run renovate
        env:
          PAT: ${{ secrets.PAT }}
          GITHUB_COM_TOKEN: ${{ secrets.GITHUB }}
        run: |
          echo "Running renovate"
          cd ${GITHUB_WORKSPACE}
          renovate --token ${PAT}

The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as 'action secrets' within the renovate repository.

Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.