[BLOG] tutorial to run Forgejo as a service in Woodpecker #55

Copy link

Ghost commented 2023年01月12日 19:07:35 +01:00

s/14/15/ to be consistent with the file name

s/14/15/ to be consistent with the file name

Ghost commented 2023年01月12日 19:09:15 +01:00

Suggestion: add "(that is what detach: true is for)"

Suggestion: add "(that is what `detach: true` is for)"

Ghost commented 2023年01月12日 19:09:47 +01:00

s/wich/script which/

s/wich/script which/

circlebuilder commented 2023年01月13日 06:03:16 +01:00

Somewhat confusing when unfamiliar with Forgejo and/or Woodpecker. I infer that "just as MySQL" means that the CI runs as user MySQL? The summary may also include mention why I should consider that, which isn't clear in the article yet (other than somehow related to running tests).

Somewhat confusing when unfamiliar with Forgejo and/or Woodpecker. I infer that "just as MySQL" means that the CI runs as user `MySQL`? The summary may also include mention why I should consider that, which isn't clear in the article yet (other than somehow related to running tests).

earl-warren commented 2023年01月13日 16:56:22 +01:00

Replaced with just as a MySQL service. The reader is otherwise assumed to know Woodpecker and Forgejo otherwise it will be useless to them.

Replaced with `just as a MySQL service`. The reader is otherwise assumed to know Woodpecker and Forgejo otherwise it will be useless to them.

circlebuilder commented 2023年01月15日 09:34:01 +01:00

In follow-up to @dachary asking my feedback, I have following thoughts..

The blog says:

it is useful to run a detached (in the background, AKA a service) MySQL server, as explained in the Woodpecker CI documentation

Yet the referenced doc does not mention the usefulness. So why is it useful is an open question. Why would someone take the effort?

Other than that.. should knowledge of Woodpecker be assumed in the blog? And should knowledge of the usefulness also be assumed?

I argue that Woodpecker is not just any random CI. Instead it is THE preferred CI (say, like Forgejo's 'reference CI'). There are tons of CI softwares, but this is the one that has Forgejo's special attention. And also it is the one that Codeberg has adopted for similar reasons, and for which they offer an integrated CI service for.

Given all that a bit more introductive text would be my recommendation, so that people learn about Forgejo's preferred approach (and the nice FOSS alignment it brings, which is part of project philosophy).

In follow-up to @dachary asking my feedback, I have following thoughts.. The blog says: > it is useful to run a detached (in the background, AKA a service) MySQL server, as explained in [the Woodpecker CI documentation](https://woodpecker-ci.org/docs/next/usage/services) Yet the referenced doc does not mention the usefulness. So why is it useful is an open question. Why would someone take the effort? Other than that.. should knowledge of Woodpecker be assumed in the blog? And should knowledge of the usefulness also be assumed? I argue that Woodpecker is not just any random CI. Instead it is THE preferred CI (say, like Forgejo's 'reference CI'). There are tons of CI softwares, but this is the one that has Forgejo's special attention. And also it is the one that Codeberg has adopted for similar reasons, and for which they offer an integrated CI service for. Given all that a bit more introductive text would be my recommendation, so that people learn about Forgejo's preferred approach (and the nice FOSS alignment it brings, which is part of project philosophy).

circlebuilder commented 2023年01月13日 05:57:21 +01:00

it is useful to run a detached (in the background, AKA a service) MySQL server

I would wonder here: Why in particular is it useful? I could not find that in the Woodpecker doc as well, so maybe a bit of extra explanation may be given.

For that to work, the initial user is provided as an environment variable and created when the server starts.

I do not see the env variable that sets a user. Maybe for someone in-the-know of Woodpecker this is obvious, but for someone new / just-curious, this is confusing.

> it is useful to run a detached (in the background, AKA a service) MySQL server I would wonder here: Why in particular is it useful? I could not find that in the Woodpecker doc as well, so maybe a bit of extra explanation may be given. > For that to work, the initial user is provided as an environment variable and created when the server starts. I do not see the env variable that sets a user. Maybe for someone in-the-know of Woodpecker this is obvious, but for someone new / just-curious, this is confusing.

earl-warren commented 2023年01月13日 16:58:22 +01:00

This is indeed obvious to a Woodpecker CI user. See https://woodpecker-ci.org/docs/next/usage/services

This is indeed obvious to a Woodpecker CI user. See https://woodpecker-ci.org/docs/next/usage/services

circlebuilder commented 2023年01月13日 05:43:50 +01:00

Using yaml after the 3 back-ticks will likely give color highlighting.

Using `yaml` after the 3 back-ticks will likely give color highlighting.

circlebuilder commented 2023年01月13日 05:44:21 +01:00

Same, highlighting as json may look better.

Same, highlighting as `json` may look better.