Livio Ribeiro

Right now it is not possible to do that automatically. But since it is an interesting feature, I am considering implementing it.

This is quite interesting. Have this approach slowed down your build times? I will take a look a this, but if you wish, feel free to open a pull request.

cargo-reame does not use cargodoc, it uses its own parser. I will take a look at it, as soon as I can

Does the badges work if we just replace `.org` with `.com`? If yes, then we can just use `.com`

That's interesting, I will look at it as soon as I can

cargo-readme is aware of these two badges, I will take a look at this as soon as I can

Sorry for taking too long to reply. Unfortunatelly, that link location is way too specific of rust doc and would required cargo-readme to do a lot more than it does...

``` 10:07:01.48 INFO ==> ** Starting LDAP setup ** 10:07:01.51 INFO ==> Validating settings in LDAP_* env vars 10:07:01.51 INFO ==> Initializing OpenLDAP... 10:07:01.51 DEBUG ==> Ensuring expected directories/files exist......

After testing a bit more, I found out that, when using a custom ldif, the object `dn: dc=example,dc=org` is not created

It is problably it, with custom ldifs the root object is not created. If the custom ldif create the root object before the other objects, container starts fine.