Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Fix links still pointing to old documentation site.

Browse source 
As mentioned in a comment on issue #4.
This commit is contained in:
Bussi Andrea 2022-04-11 00:20:40 +02:00
parent fae7c6abda
commit 50d59f41df
6 changed files with 10 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/sysadmin_guide/pages/anitya.adoc
View file

@ -86,9 +86,9 @@ Anitya on production.
==== Configuration
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
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
xref:ansible.adoc[permissions
to run the Ansible playbook].
All the following commands should be run from batcave01.

3
modules/sysadmin_guide/pages/ansible.adoc
View file

@ -235,8 +235,7 @@ Templates use the jinja2 syntax.
== rdiff-backups
see:
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/rdiff-backup.html
See: xref:rdiff-backup.adoc[]
== Additional Reading/Resources

4
modules/sysadmin_guide/pages/hotness.adoc
View file

@ -66,9 +66,9 @@ the-new-hotness on production.
==== Configuration
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
https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
xref:ansible.adoc[permissions
to run the Ansible playbook].
All the following commands should be run from batcave01.

5
modules/sysadmin_guide/pages/index.adoc
View file

@ -5,7 +5,7 @@ Welcome to The Fedora Infrastructure system administration guide.
== Getting Started
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
involved in the
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
procedures for Fedora Infrastructure applications. For information 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
Standard Operating Procedures].
xref:developer_guide:sops.adoc[Developing Standard Operating Procedures].

4
modules/sysadmin_guide/pages/requestforresources.adoc
View file

@ -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
need a review in the near future. In the request for the security audit,
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
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
to the instance when those who know it well are not available?
* 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].
* MUST tag in the security officer in the ticket so an audit can be
scheduled, including the results of the Security Policy evaluation.