Feed sync

[syspect-sec]

What

The comprehensive guide to new and legacy feed sync tools is now available.

Why

Provide users with a comprehensive guide to Greenbone feed sync tooling

Checklist

• entry added to changelog.md
• most recent changes to greenbone/docs main branch have been merged

[syspect-sec]

Although the auto merge fails (Build the Greenbone Documentation / Build Documentation (pull_request) ) due to during the auto build, myst reports an error: /home/runner/work/docs/docs/src/feed-sync.md:37: WARNING: 'myst' cross-reference target not found: 'available-feed-types' [myst.xref_missing], the upon second compile, the docs build fine and even after the first, build, (and second) the link is active and works to redirect to the correct location.

Interestingly, although the Greenbone docs use the same syntax for inline, same page links in other places, I cannot find any reference for using the [link-text](#header-title) method on either the commonmark.org markdown tutorial, or the recommended syntax guide. Although, the [link-text](#header-title) method seems to use the standard HTML internal linking syntax to headers by name, so I guess that's why it works even though it's not officially supported?

Also, I have tracked down the issue to seems to be all fourth level header links, and I've opened an issue on the MySTParser GitHub page.

[cfi-gb]

Note that the deprecated / old greenbone-nvt-sync has been now removed completely in the scanner with / since greenbone/openvas-scanner#1589 so some adjustments to this PR might be required.

[y0urself]

I need more time for review ... but I am not fine with some formulations.

Especially the "Greenbone version" stuff is a no-go. We need to communicate our products and their versions explicitly. We do not have a "Greenbone" in version x.y ...

Will do some more suggestions, when I have time.

[colinmollenhour]

The current instructions at https://greenbone.github.io/docs/latest/ are broken because the nginx config references a "feed-key" upstream but there is no such container provided by the docker-compose.yaml file. This causes the nginx container to fail to start.

Is this related?

upstream feed-key {
server feed-key:3000 max_fails=3 fail_timeout=30s;
resolver 127.0.0.11 valid=30s;
resolver_timeout 10s;
}
server {
...
location /service/feed-key/ {
proxy_pass http://feed-key/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
...
}

[cfi-gb]

@colinmollenhour This seems to be actually unrelated to this older PR, see here for the feed-key topic:

• Update Compose File #617
• Nginx doesn't start #616

[bjoernricks]

Is this related?

Not at all.