diff options
4 files changed, 70 insertions, 0 deletions
diff --git a/doc/forum/Adding_support_for_a_SQL_server/comment_2_e18fc448f51478617e5b2b9b05ce4a0f._comment b/doc/forum/Adding_support_for_a_SQL_server/comment_2_e18fc448f51478617e5b2b9b05ce4a0f._comment new file mode 100644 index 00000000..74654902 --- /dev/null +++ b/doc/forum/Adding_support_for_a_SQL_server/comment_2_e18fc448f51478617e5b2b9b05ce4a0f._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Nicolas.Schodet" + avatar="http://cdn.libravatar.org/avatar/0d7ec808ec329d04ee9a93c0da3c0089" + subject="comment 2" + date="2018-06-19T18:56:28Z" + content=""" +I am looking for a solution which could be integrated to propellor. Is it possible to include those additional libraries in propellor sources and have them included in the build on demand? I am not very familiar with the haskell build systems. + +About generated passwords, a nice solution would be to do it in PrivData. The user would provide a salt as the private data and it would be combined to context to generate a password. I can try find how this could be done. +"""]] diff --git a/doc/forum/Adding_support_for_a_SQL_server/comment_3_14b6968853d30a2054cc675c6005f29f._comment b/doc/forum/Adding_support_for_a_SQL_server/comment_3_14b6968853d30a2054cc675c6005f29f._comment new file mode 100644 index 00000000..b566f3c5 --- /dev/null +++ b/doc/forum/Adding_support_for_a_SQL_server/comment_3_14b6968853d30a2054cc675c6005f29f._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2018-06-23T19:13:59Z" + content=""" +Well, cabal files can have flags that enable additional dependencies, but +using them complicates testing the program since you have to try building +it with different combinations of flags. And deploying propellor with the +desired flags turned on would be an additional complication. + +I feel that additional libraries that depend on propellor and the sql +library and provide properties is a better approach. The user can easily +add the dependency to their ~/.propellor/config.cabal, and the necessary +dependencies will be automatically installed when propellor is deploying +itself to a new host. +"""]] diff --git a/doc/forum/DNS_-_Support_for_Multiline_TXT_records.mdwn b/doc/forum/DNS_-_Support_for_Multiline_TXT_records.mdwn new file mode 100644 index 00000000..69a62b59 --- /dev/null +++ b/doc/forum/DNS_-_Support_for_Multiline_TXT_records.mdwn @@ -0,0 +1,19 @@ +bind9 has a limit on the number of characters in a single line TXT record. I was unable to provision the DKIM TXT record using propellor due to this limit. + +I added a new MTXT record type to `Propellor.Types.DNS.Record` ([patch][1]). + +MTXT creates a multiline TXT record. It splits the record's text (say +"long string...\n...xyz") at `'\n'` and creates a TXT record of the +form: + + + domain IN TXT ( "long string..." + "...xyz" ) + + +I'm [currently using this recipe][2] to provision the DKIM TXT record. + +I want to know if there is a better way to do this without having to add the MTXT record type? + +[1]: https://ricketyspace.net/file/0001-add-MTXT-record-type-to-Propellor.Types.DNS.Record.patch +[2]: https://git.ricketyspace.net/propellor/tree/config.hs#n722 diff --git a/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment b/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment new file mode 100644 index 00000000..5595af19 --- /dev/null +++ b/doc/forum/DNS_-_Support_for_Multiline_TXT_records/comment_1_b97c158ae4e3abb6e4c90a2c91e0c207._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-06-23T18:42:32Z" + content=""" +It seems that the limit is 255 characters, and this +limit applies to any string in a bind zone file, +rather than being a maximim line length. A single line can contain multiple +such strings, although there's probably a maximum line length somewhere +too, so using parens to extend across multiple lines is wise. + +The values inside the parens are concacenated together, no newline is added +to the string that bind builds up from them AFAICS. + +So it seems your code is stripping out the newlines from the TXT value. +Which probably doesn't matter for DKIM public key material, +and I don't think that bind zone files support multiline strings anyway. +But a single line could be too long and splitting on newlines would not +help then. + +So, I think the thing to do would be to make `rValue` break TXT +strings into substrings no longer than 255 characters. Then you don't +need a new constructor, and long SSHFP etc records could also be handled +that way. +"""]] |