known

Blogging, meet social. Known is a social publishing platform.

GitHub repo: https://github.com/idno/Known-Docker

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at https://hub.docker.com/images/known

Supported tags and respective Dockerfile links

• 0.9.9, 0.9, 0, latest

Quick reference

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

• Where to file issues:
  https://github.com/idno/Known-Docker/issues

• Maintained by:
  Known

• Supported architectures: (more info)
  amd64, arm64v8

• Published image artifact details:
  repo-info repo’s repos/known/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/known
  official-images repo’s library/known file (history)

• Source of this description:
  docs repo’s known/ directory (history)

• Supported Docker versions:
  the latest release (down to 1.6 on a best-effort basis)

Known: social publishing for groups and individuals

Blogging, meet social.

Known is a social publishing platform. Publish on your own site, reach your audience across social media.

How to use this image

docker run --link some-mysql:db -d known

Now you can get access to fpm running on port 9000 inside the container. If you want to access it from the Internets, we recommend using a reverse proxy in front. You can find more information on that on the docker-compose section.

The following environment variables are also honored for configuring your Known instance:

• -e KNOWN_DB_HOST=... (defaults to the IP and port of the linked mysql container)
• -e KNOWN_DB_USER=... (defaults to “root”)
• -e KNOWN_DB_PASSWORD=... (defaults to the value of the MYSQL_ROOT_PASSWORD environment variable from the linked mysql container)
• -e KNOWN_DB_NAME=... (defaults to “known”)
• -e MAIL_HOST=...
• -e MAIL_PORT=...
• -e MAIL_SECURE=... (“starttls” for instance)
• -e MAIL_USER=...
• -e MAIL_PASS=...

If the KNOWN_DB_NAME specified does not already exist on the given MySQL server, it will be created automatically upon startup of the known container, provided that the KNOWN_DB_USER specified has the necessary permissions to create it.

If you’d like to use an external database instead of a linked mysql container, specify the hostname and port with KNOWN_DB_HOST along with the password in KNOWN_DB_PASSWORD and the username in KNOWN_DB_USER (if it is something other than root):

$ docker run --name some-known -e KNOWN_DB_HOST=10.1.2.3:3306 \
    -e KNOWN_DB_USER=... -e KNOWN_DB_PASSWORD=... -d known

Via docker-compose

You can use a setup that is used in production at IndieHosters/known.

Installation

Once started, you’ll arrive at the configuration wizard. Follow the steps as indicated.

Contribute

Pull requests are very welcome!

We’d love to hear your feedback and suggestions in the issue tracker: github.com/idno/Known-docker/issues.

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s known/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.