Fix links still pointing to old documentation site.
As mentioned in a comment on issue #4.
This commit is contained in:
parent
fae7c6abda
commit
50d59f41df
6 changed files with 10 additions and 12 deletions
|
@ -30,7 +30,7 @@ runs MAY be exempted from this check.
|
||||||
|
|
||||||
The application MUST use OpenID Connect to authenticate users. The
|
The application MUST use OpenID Connect to authenticate users. The
|
||||||
application MUST use an
|
application MUST use an
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/auth.html#libraries[approved
|
xref:developer_guide:auth.adoc#_libraries[approved
|
||||||
authentication library]. If the application supports an API, it SHOULD
|
authentication library]. If the application supports an API, it SHOULD
|
||||||
accept OpenID Connect Bearer tokens, which MUST be verified by the
|
accept OpenID Connect Bearer tokens, which MUST be verified by the
|
||||||
approved authentication library. The application MUST NOT accept any
|
approved authentication library. The application MUST NOT accept any
|
||||||
|
|
|
@ -86,9 +86,9 @@ Anitya on production.
|
||||||
==== Configuration
|
==== Configuration
|
||||||
|
|
||||||
To deploy the new configuration, you need
|
To deploy the new configuration, you need
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/sshaccess.html[ssh
|
xref:sshaccess.adoc[ssh
|
||||||
access] to batcave01.iad2.fedoraproject.org and
|
access] to batcave01.iad2.fedoraproject.org and
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
|
xref:ansible.adoc[permissions
|
||||||
to run the Ansible playbook].
|
to run the Ansible playbook].
|
||||||
|
|
||||||
All the following commands should be run from batcave01.
|
All the following commands should be run from batcave01.
|
||||||
|
|
|
@ -235,8 +235,7 @@ Templates use the jinja2 syntax.
|
||||||
|
|
||||||
== rdiff-backups
|
== rdiff-backups
|
||||||
|
|
||||||
see:
|
See: xref:rdiff-backup.adoc[]
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/rdiff-backup.html
|
|
||||||
|
|
||||||
== Additional Reading/Resources
|
== Additional Reading/Resources
|
||||||
|
|
||||||
|
|
|
@ -66,9 +66,9 @@ the-new-hotness on production.
|
||||||
==== Configuration
|
==== Configuration
|
||||||
|
|
||||||
To deploy the new configuration, you need
|
To deploy the new configuration, you need
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/sshaccess.html[ssh
|
xref:sshaccess.adoc[ssh
|
||||||
access] to _batcave01.iad2.fedoraproject.org_ and
|
access] to _batcave01.iad2.fedoraproject.org_ and
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
|
xref:ansible.adoc[permissions
|
||||||
to run the Ansible playbook].
|
to run the Ansible playbook].
|
||||||
|
|
||||||
All the following commands should be run from batcave01.
|
All the following commands should be run from batcave01.
|
||||||
|
|
|
@ -5,7 +5,7 @@ Welcome to The Fedora Infrastructure system administration guide.
|
||||||
== Getting Started
|
== Getting Started
|
||||||
|
|
||||||
If you haven't already, you should complete the general
|
If you haven't already, you should complete the general
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/index.html#getting-started[Getting Started] guide.
|
xref:developer_guide:getting-started.adoc[Getting Started] guide.
|
||||||
Once you've completed that, you're ready to get
|
Once you've completed that, you're ready to get
|
||||||
involved in the
|
involved in the
|
||||||
https://accounts.fedoraproject.org/group/fi-apprentice/[Fedora
|
https://accounts.fedoraproject.org/group/fi-apprentice/[Fedora
|
||||||
|
@ -68,5 +68,4 @@ infrastructure ticket you are working on. It will then be reviewed.
|
||||||
Below is a table of contents containing all the standard operating
|
Below is a table of contents containing all the standard operating
|
||||||
procedures for Fedora Infrastructure applications. For information on
|
procedures for Fedora Infrastructure applications. For information on
|
||||||
how to write a new standard operating procedure, consult the guide on
|
how to write a new standard operating procedure, consult the guide on
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/sops.html#develop-sops[Developing
|
xref:developer_guide:sops.adoc[Developing Standard Operating Procedures].
|
||||||
Standard Operating Procedures].
|
|
||||||
|
|
|
@ -90,7 +90,7 @@ infrastucture list explaining the testing done and inviting comment.
|
||||||
Also, the security officer should be informed that a new service will
|
Also, the security officer should be informed that a new service will
|
||||||
need a review in the near future. In the request for the security audit,
|
need a review in the near future. In the request for the security audit,
|
||||||
please add the results of self-evaluation of the
|
please add the results of self-evaluation of the
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/security_policy.html[Application
|
xref:developer_guide:security_policy.adoc[Application
|
||||||
Security Policy]. Any deviations from the policy _must_ be noted in the
|
Security Policy]. Any deviations from the policy _must_ be noted in the
|
||||||
request for audit.
|
request for audit.
|
||||||
|
|
||||||
|
@ -105,7 +105,7 @@ the resource would be best deployed should be determined.
|
||||||
SOP? A troubleshooting SOP? Any other tasks that might need to be done
|
SOP? A troubleshooting SOP? Any other tasks that might need to be done
|
||||||
to the instance when those who know it well are not available?
|
to the instance when those who know it well are not available?
|
||||||
* MUST perform self-evaluation of the
|
* MUST perform self-evaluation of the
|
||||||
https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/security_policy.html[Application
|
xref:developer_guide:security_policy.adoc[Application
|
||||||
Security Policy].
|
Security Policy].
|
||||||
* MUST tag in the security officer in the ticket so an audit can be
|
* MUST tag in the security officer in the ticket so an audit can be
|
||||||
scheduled, including the results of the Security Policy evaluation.
|
scheduled, including the results of the Security Policy evaluation.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue