ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

fix markdown links

Browse source
This commit is contained in:
Michael DeHaan 2012-02-27 23:38:21 -05:00
parent d8c0be9ae6
commit c8005e6c60
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -75,7 +75,7 @@ Other than the comamnd module, though, ansible modules are not scripts. They ma
the remote system look like you state, and run the commands neccessary to get it
there.
(Read the manpage)[https://github.com/mpdehaan/ansible/blob/master/docs/man/man1/ansible.1.asciidoc]
[Read the manpage](https://github.com/mpdehaan/ansible/blob/master/docs/man/man1/ansible.1.asciidoc)
File Transfer
=============
@ -118,7 +118,7 @@ Other Modules
=============
See the library directory for lots of extras. There's also a manpage,
(ansible-modules(5))[https://github.com/mpdehaan/ansible/blob/master/docs/man/man5/ansible-modules.5.asciidoc] that covers all the options they take. You can
[ansible-modules(5)](https://github.com/mpdehaan/ansible/blob/master/docs/man/man5/ansible-modules.5.asciidoc) that covers all the options they take. You can
read the asciidoc in github in the 'docs' directory.
Playbooks
@ -129,7 +129,7 @@ together, and can even fire off triggers when certain commands report changes.
They are the basis for a really simple configuration management system, unlike
any that already exist. Powerful, concise, but dead simple.
See examples/playbook.yml for what the syntax looks like, and the manpage -- (ansible-playbook(5))[https://github.com/mpdehaan/ansible/blob/master/docs/man/man5/ansible-playbook.5.asciidoc] for more details.
See examples/playbook.yml for what the syntax looks like, and the manpage -- [ansible-playbook(5)](https://github.com/mpdehaan/ansible/blob/master/docs/man/man5/ansible-playbook.5.asciidoc) for more details.
To run a playbook: