nico/www.nico.schottelius.org
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

cdist doc update

Browse source
This commit is contained in:
Darko Poljak 2016-08-22 18:53:07 +02:00
parent 9d0435bb6b
commit 140bb1bf04
4 changed files with 10 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
software/cdist/features.mdwn
View file

@ -3,7 +3,7 @@ But cdist ticks differently, here is the feature set that makes it unique:
[[!table data=""" [[!table data="""
Keywords | Description Keywords | Description
Simplicity | There is only one type to extend cdist called ***type*** Simplicity | There is only one type to extend cdist called ***type***
Design | Type and core cleanly seperated Design | Type and core cleanly separated
Design | Sticks completly to the KISS (keep it simple and stupid) paradigma Design | Sticks completly to the KISS (keep it simple and stupid) paradigma
Design | Meaningful error messages - do not lose time debugging error messages Design | Meaningful error messages - do not lose time debugging error messages
Design | Consistency in behaviour, naming and documentation Design | Consistency in behaviour, naming and documentation

5
software/cdist/support.mdwn
View file

@ -8,7 +8,7 @@ You can join the development ***IRC channel***
### Mailing list ### Mailing list
Bug reports, questions, patches, etc. should be send to the Bug reports, questions, patches, etc. should be send to the
[cdist mailing list](http://l.schottelius.org/mailman/listinfo/cdist). [cdist mailing list](https://groups.google.com/forum/#!forum/cdist-configuration-management).
### Linkedin ### Linkedin
@ -17,6 +17,9 @@ at [Linked in](http://www.linkedin.com/),
you can join the you can join the
[cdist group](http://www.linkedin.com/groups/cdist-configuration-management-3952797). [cdist group](http://www.linkedin.com/groups/cdist-configuration-management-3952797).
### Chat
Chat with us: [ungleich chat] (https://chat.ungleich.ch/channel/cdist).
### Commercial support ### Commercial support
You can request commercial support for cdist from You can request commercial support for cdist from

6
software/cdist/update.mdwn
View file

@ -67,7 +67,7 @@ Use [messaging](/software/cdist/man/3.0.0/man7/cdist-messaging.html) instead.
### Updating from 2.2 to 2.3 ### Updating from 2.2 to 2.3
No incompatiblities. No incompatibilities.
### Updating from 2.1 to 2.2 ### Updating from 2.1 to 2.2
@ -134,7 +134,7 @@ Have a look at the update guide for [[2.0 to 2.1|2.0-to-2.1]].
### Updating from 1.3 to 1.5 ### Updating from 1.3 to 1.5
No incompatiblities. No incompatibilities.
### Updating from 1.2 to 1.3 ### Updating from 1.2 to 1.3
@ -142,7 +142,7 @@ Rename **gencode** of every type to **gencode-remote**.
### Updating from 1.1 to 1.2 ### Updating from 1.1 to 1.2
No incompatiblities. No incompatibilities.
### Updating from 1.0 to 1.1 ### Updating from 1.0 to 1.1

4
software/cdist/update/2.0-to-2.1.mdwn
View file

@ -10,7 +10,7 @@ explorers and manifest to custom directories.
This document will guide you to a successful update. This document will guide you to a successful update.
## Preperation ## Preparation
As for every software and system you use in production, you should first of As for every software and system you use in production, you should first of
all make a backup of your data. To prevent any breakage, it is all make a backup of your data. To prevent any breakage, it is
@ -35,7 +35,7 @@ Now try to merge upstream into the new branch.
% git merge origin/2.1 % git merge origin/2.1
Fix any conflicts that may have been occurred due to local changes Fix any conflicts that may have been occurred due to local changes
and then **git add** and *git commit** those changes. This should seldomly and then **git add** and *git commit** those changes. This should seldom
occur and if, it's mostly for people hacking on the cdist core. occur and if, it's mostly for people hacking on the cdist core.
## Move "conf" directory ## Move "conf" directory