Skip to content
This repository has been archived by the owner on Jul 16, 2022. It is now read-only.

Request: Provide Docker container for self-hosters #51

Open
cryptochrome opened this issue Jan 30, 2017 · 3 comments
Open

Request: Provide Docker container for self-hosters #51

cryptochrome opened this issue Jan 30, 2017 · 3 comments
Labels
type: Feature Issues that request or implement a new feature or module type: Suggestion Issues that suggest source changes type: Third-Party Issues that discuss or fix Third-Party changes

Comments

@cryptochrome
Copy link

It would be super efficient and easy for all self-hosters if they could simply pull a docker image and run the bot in a container. That way everything could be provided by the maintainer and self-hosters would not have to deal with stuff they have no clue about (like node.js, mongoDB etc.).

@Gilbert142 Gilbert142 added type: Feature Issues that request or implement a new feature or module type: Third-Party Issues that discuss or fix Third-Party changes labels Jan 31, 2017
@Gilbert142
Copy link
Member

While this is a good idea, and defo something to work on, simply babysitting un-experienced self-hosters is not a good idea. We're going to have to do some stuff that unexperienced self-hosters won't understand at some point.

@cryptochrome
Copy link
Author

I agree on the babysitting part. Docker has a lot of other advantages though :)

@HilbertGilbertson HilbertGilbertson added the type: Suggestion Issues that suggest source changes label Feb 1, 2017
@0sean
Copy link

0sean commented Apr 5, 2017

Docker would be a cool idea, as there are certain ways to add auto-updating, so people can simply wait for it to update, but I agree, we shouldn't babysit un-experienced self-hosters (I think self-hosting is easy enough to do/learn anyways).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: Feature Issues that request or implement a new feature or module type: Suggestion Issues that suggest source changes type: Third-Party Issues that discuss or fix Third-Party changes
Projects
None yet
Development

No branches or pull requests

4 participants