Beginner's Guide: Hugo + Gitlab CI + Surfer

[robi]

does gitea or gogs not have any CI?

[girish]

@robi I think they only integrate with existing CI systems like drone.

[A Former User]

@robi Drone is the best one right now. @fbartels did offer to package it if there was interest and I believe he wanted it to be sponsored. I would check that out.

[fbartels]

Drone indeed integrates quite easily with Gitea. More information on my app offering can be found at https://forum.cloudron.io/topic/3350/offered-drone-ci-on-cloudron

The one thing I particularly like is that I only need the "Dashboard" to be centrally hosted, all the job runners can run inside private networks. The runner is a small golang binary that can easily be launched with docker-compose. This allows me to simply start the runner on whatever device I am currently working (desktop, laptop, chromebook, mini homeserver).

This is my drone configuration to build my hugo site and deploy it to my surfer instance:

---
kind: pipeline
name: blog
concurrency:
  limit: 1
steps:
  - name: submodules
    image: alpine/git
    commands:
      - git submodule update --init --recursive --remote
  - name: build
    image: plugins/hugo
    settings:
      hugo_version: 0.79.0
      extended: true
      validate: true
  - name: deploy
    image: 'fbartels/cloudron-surfer:5.12.2'
    environment:
      SURFTOKEN:
        from_secret: surftoken
    commands:
      - surfer --version
      - touch public/ # touch folder to avoid problems with timestamps
      - surfer put --token $SURFTOKEN --server blog.9wd.eu ./public/* /
    when:
      branch:
        - master
      event:
        exclude:
          - pull_request
  - name: Notification Rocket.Chat
    image: rmilewski/drone-rocket:latest
    when:
      status:
        - success
        - failure
    settings:
      webhook: https://chat.9wd.eu/hooks/$(ROCKETSECRET)
      username: rocket.cat
      channel: drone
      color:
        - value: green
          when:
            DRONE_BUILD_STATUS: success
        - value: red
          when:
            DRONE_BUILD_STATUS: failure
      message:
        - value: "Build: ${DRONE_BUILD_NUMBER} succeeded. Good job."
          when:
            DRONE_BUILD_STATUS: success
        - value: "Build: ${DRONE_BUILD_NUMBER} failed. Fix me please."
      text: ${DRONE_COMMIT_MESSAGE}
      fields:
        - title: Author
          value: ${DRONE_COMMIT_AUTHOR}
        - title: Demo
          value: "This field will only be visible if the current branch: ${DRONE_COMMIT_BRANCH} is master or production"
          when:
            DRONE_COMMIT_BRANCH:
              - master
              - production

[girish]

@fbartels IIRC, a complication with packaging drone was that it required ENV vars to be set before the app is even started. Like you have to select the integration type etc. Is that still the case? If so, how would a Cloudron installation UX for this look like? Just choose some default and let the user edit the config file?

[robi]

@girish bring up the app with first run instructions then on restart it reconfigures to prod.

[fbartels]

@girish kind of what @robi said. At first startup it creates a config file in the app that still needs to be manually edited in regards to where Gitea can be reached as well as its configured client id and secret.

I did add you to the repo a while ago, so you can also have a direct look at https://github.com/fbartels/cloudron-drone-app/

[jdaviescoates]

@fbartels said in Beginner's Guide: Hugo + Gitlab CI + Surfer:

I did add you to the repo a while ago, so you can also have a direct look at https://github.com/fbartels/cloudron-drone-app/

I'm getting a 404 there.

[A Former User]

@jdaviescoates Its a private repo. He'd have to invite you to it via your Github account.

[fbartels]

@jdaviescoates it's a private repo. You can get access by sponsoring me on GitHub. More details at https://forum.cloudron.io/topic/3350/offered-drone-ci-on-cloudron

[A Former User]

@fbartels Beat me to it :^)

[fbartels]

@atrilahiji i would have said it's the other way around

[jdaviescoates]

@atrilahiji @fbartels ah, I see, thanks

[vjvanjungg]

@atrilahiji that would be great if you could shed some light on it. it’d be cool! I totally forgot about the self-host side of things earlier. Added the note.