Codeberg Documentation – tutorials, how-tos and other Codeberg-specific resources.
Find a file
Dependency bot 8f5231283e chore: Configure Renovate (#433)
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---
### Detected Package Files

 * `Dockerfile` (dockerfile)
 * `package.json` (npm)

### Configuration Summary

Based on the default config's presets, Renovate will:

  - Start dependency updates only once this onboarding PR is merged
  - Enable Renovate Dependency Dashboard creation.
  - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
  - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.
  - Run lock file maintenance (updates) early Monday mornings.
  - Schedule automerge daily.
  - Schedule for weekends.
  - Enable Renovate Dependency Dashboard creation.
  - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
  - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.
  - Run lock file maintenance (updates) early Monday mornings.
  - Schedule automerge daily.
  - Schedule for weekends.
  - Run Renovate on following schedule: every weekend

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.

---

### What to Expect

With your current configuration, Renovate will create 5 Pull Requests:

<details>
<summary>chore(deps): update dependency pagefind to v1.1.0</summary>

  - Schedule: ["every weekend"]
  - Branch name: `renovate/pagefind-1.x-lockfile`
  - Merge into: `main`
  - Upgrade [pagefind](https://github.com/CloudCannon/pagefind) to `1.1.0`

</details>

<details>
<summary>chore(deps): update font awesome to v6.5.2</summary>

  - Schedule: ["every weekend"]
  - Branch name: `renovate/font-awesome`
  - Merge into: `main`
  - Upgrade [@fortawesome/fontawesome-svg-core](https://github.com/FortAwesome/Font-Awesome) to `6.5.2`
  - Upgrade [@fortawesome/free-solid-svg-icons](https://github.com/FortAwesome/Font-Awesome) to `6.5.2`

</details>

<details>
<summary>chore(deps): update dependency markdown-it-anchor to v9</summary>

  - Schedule: ["every weekend"]
  - Branch name: `renovate/markdown-it-anchor-9.x`
  - Merge into: `main`
  - Upgrade [markdown-it-anchor](https://github.com/valeriangalliat/markdown-it-anchor) to `^9.0.0`

</details>

<details>
<summary>chore(deps): update node.js to v16</summary>

  - Schedule: ["every weekend"]
  - Branch name: `renovate/node-16.x`
  - Merge into: `main`
  - Upgrade [node](https://github.com/nodejs/node) to `16.15.1-stretch-slim`

</details>

<details>
<summary>chore(deps): lock file maintenance</summary>

  - Schedule: ["before 4am on Monday"]
  - Branch name: `renovate/lock-file-maintenance`
  - Merge into: `main`
  - Regenerate lock files to use latest dependency versions

</details>

<br />

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for `prhourlylimit` for details.

---

 Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

<!--renovate-config-hash:67259f1d62398ce599523778399b8abd7a312190509ac1958cd9cc122e7196ad-->

Co-authored-by: woodpecker-bot <woodpecker-bot@obermui.de>
Co-authored-by: pat-s <pat-s@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/433
Co-authored-by: Dependency bot <renovate-bot@noreply.codeberg.org>
Co-committed-by: Dependency bot <renovate-bot@noreply.codeberg.org>
2024-06-11 07:47:06 +00:00
assets Automatically generate Table of Contents for each page (#376) 2023-12-11 17:32:09 +00:00
content Codeberg Pages: Add warning for setting up records on some registrars (#431) 2024-06-09 14:23:36 +00:00
.eleventy.js Automatically generate Table of Contents for each page (#376) 2023-12-11 17:32:09 +00:00
.gitignore Initial version of a Markdown documentation (#221) 2022-04-23 21:18:08 +02:00
deploy.sh pages compatibility for deployment 2022-05-18 18:42:20 +02:00
Dockerfile Add Dockerfile to serve documentation 2022-04-14 12:34:21 +02:00
LICENSE.md Add info about fonts and icons used in the website 2022-08-23 16:21:29 +02:00
package-lock.json Automatically generate Table of Contents for each page (#376) 2023-12-11 17:32:09 +00:00
package.json Automatically generate Table of Contents for each page (#376) 2023-12-11 17:32:09 +00:00
pagefind.yml Add search functionality (#370) 2023-11-30 21:33:22 +00:00
README.md Add search functionality (#370) 2023-11-30 21:33:22 +00:00
renovate.json chore: Configure Renovate (#433) 2024-06-11 07:47:06 +00:00

Codeberg Documentation

This repository contains the documentation for Codeberg, with some code to build it into a static website.

Please have a look into it and consider to help writing the Documentation. This is still very much work-in-progress, the more useful material we collect, the better we can later present it! All contributions are very welcome!

For an introduction on contributing to Codeberg Documentation, please have a look at the section on improving the documentation.

Usage

Local Development

If you want to work on the documentation, for example by writing your own articles, the easiest way to do so is to fork the documentation repository and develop locally.

First, run

npm install

to install all dependencies (they will be installed only for this project, not globally). You only have to do this once.

Then run

npm run serve

to start a development web server that by default is listening at http://localhost:8080.

Now you can simply change, add or remove files, save them and the development server should automatically reload all changed pages using the amazing Browsersync.

When you're done, commit your changes to your fork and write a pull request for Codeberg/Documentation. We're happy about every contribution!

Local development using the Dockerfile

If you do not have nodejs installed or do not want to run the development web server directly on your host, you can also use a docker container.

You must have a container-engine installed (docker, podman, etc.)

First build the container image:

docker build -t codeberg/documentation-server .

You do not have to rebuild the image every time. Once you build the image you can always start the development webserver using the container engine:

docker run --rm -v $PWD:/opt/documentation codeberg/documentation-server:latest

Use the "External" URL the container outputs on startup to access your documentation.

Changes to files in the documentation are reflected in the browser as the server regularly updates the generated files.

Use Ctrl-C to exit / end the container.

The parameters are:

--rm removes the container after it's use -v mounts the current (documentation repository root) folder to /opt/documentation in the container.

codeberg/documentation-server:latest refers to the container image built in the first step (using docker build).

Build & Deployment

Like for local development, before building and deploying you first have to install the dependencies (once):

npm install

To build the entire website to the _site directory run

npm run build

Instead, to directly publish the page to Codeberg pages, you can also run

npm run deploy

which includes a call to npm run build.

Technical Information

This website uses Eleventy, a static site generator.

It's supplied as a dev-dependency in package.json and its dependencies are locked with package-lock.json to try to ensure reproducible builds.

It also uses PageFind, a static search library.

License and Contributors

This website (excluding bundled fonts) is licensed under CC BY-SA 4.0. See the LICENSE file for details.

Please refer to the commit log for an exhaustive list of contributors to Codeberg Documentation.