%s/digitalocean/netbox-community/gi ...

Thank you Digitalocean for sponsoring Netbox!
And thank you for letting it grow up and move out ;)

Provides necessary changes for v2.6 compatibility ...

Fixes #139

Prepare Version 0.14.0

Prepare Version 0.13.0

Merge branch 'mryauch-patch-1' of https://github.com/mryauch/netbox-docker into mryauch-mryauch-patch-1

Prepare Version 0.12.0

Updated README.md to reflect AUTH_LDAP_BIND_PASSWORD secret support

prepare next version

Update README.md ...

Fix the link to the configuration file, since it's core was "outsourced" some time ago.

Make startup scripts optional ...

To optimize the application boot time the startup scripts can now be
disabled by an ENV variable. The default when the variable is not set,
is to run the startup scripts. This means that the default behaviour is
not changed from earlier releases.

Prepare 0.9.0

Prepare 0.8.0

Update README.md

Update README.md

Update references to netboxcommunity

Update README

add note about breaking changes

formatted

Documenting reporting usage in `README.md` ...

Updated `README.md` on how to use the reporting feature of NetBox within this container.

Update Breaking Changes list

Comply to README style

Merge branch 'master' into add-more-seeds

Update README

Add permissions to user/group initializers ...

Thank you @bdlamprecht for researching how to add permissions to
users and groups in #92.

Fixes #92

Update README.md

✏️ Listed one more breaking change

✏️ Mention update to Alpine 3.8

✏️ Added nginx troubleshooting section

✨ Use a default Redis password ...

Although it does not provide any additional security, it shows how to
configure Redis with a password and how to use Netbox using a password
protected redis server. Something that might be considered in a classic
production deployment. (But is mostly irrelevant in e.g. a Kubernetes /
OpenShift deployment as the isolation is usually on a network level.)

♻️ Make netbox-worker it's own container ...

One container should ideally have one responsibility [1]. Therefore I
implemented the netbox-worker to start in it's own container. This is
possible, because netbox and the worker communicate via redis anyway.

They still use the same image underneath, just the "command" they
execute while starting different.

Or in other words: I see no reason to introduce supervisord, when we
already have docker-compose which can take care of running multiple
processes.

Also, here's another benefit: Now it's possible to view the logs of the
webhook worker independently of the other netbox logs (and vice-versa).

Other changes in this commit:
* I don't see a reason to put a password for Redis in the docker-compose
  setup, so I removed it.
* Slightly changed the nginx config, so that the nginx startup command
  becomes simpler and any error should be visible in the docker log.
* Some housekeeping in the `Dockerfile`.
* Added some troubleshooting advice regarding webhooks to the README.

I'd like to thank Brady (@bdlamprecht [2]) here who did the harder
work of figuring out what's even required to have webhooks working. [3]

[1] 
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#decouple-applications
[2] https://github.com/bdlamprecht
[3] https://github.com/ninech/netbox-docker/pull/90