One of our near-term goals is to substantially improve documentation.
There are some areas that are pretty ok right now (http api for the
most part) and some areas that are pretty bad (admin and getting
setup). As part of this we will also focus on a lot of "getting
started" type guides and sample applications.
What areas of "getting started" and/or examples do you think would help?
Cheers,
Greg
I would like to see a getting started for setting up on AWS. Including:
What machine type/OS
Installation with optimal settings
Server Configuration including allowing remote requests
Perhaps ensuring that the EventStore starts on reboot
Anything else I am not thinking of
How to
run it as a Windows service
use Active Directory for authentication
setup a warm replica with 2 nodes or a 2 node + witness node cluster
Command line parameters need updating / fleshing out last time I checked, might have been updated since.
This page could also do with content (shows up blank for me): https://github.com/EventStore/EventStore/wiki/Subscriptions-(.NET-API)
Same thing for Azure - on a getting started white paper.
– What type of machine / disk is best / settings
– Ports to open / close / internal vs. external
– Securing the App
" run it as a Windows service
use Active Directory for authentication"
These are both included in the commercial version
I’d like to see a ‘blessed’ RPM and DEB build and more information about how to host the cluster with e.g. fleet or consul. I’m trying to set it up on docker right now to be run on CoreOS as a clustered service; that would be great to have more input on.
As you know I’ve built images for the project https://packagecloud.io/haf/oss which I think it would be great to have more feedback around - e.g. by having the core eventstore team work with the recipe to make it fully featured (upgradable, auto-run upgrade scripts, proper configuration) and to make it work well with puppet and/or other configuration management tools.
I think that having a gitter chat room would be an improvement too https://gitter.im/EventStore
Removing the dual vocabulary; what’s commercial, what’s open source - and being much more specific about what options can be purchased from you at a premium and which ones can’t.
Henrik,
Thanks for the feedback.
I’d like to see a ‘blessed’ RPM and DEB build and more information about how to host the cluster with e.g. fleet or consul. I’m trying to set it up on docker right now to be run on CoreOS as a clustered service; that would be great to have more
input on.
At this point I’m not sure we want to offer blessed feeds of the OSS product - though we’d consider doing so for the commercial one. We’ve not looked at running with docker, though I’ve used consul for other things.
As you know I’ve built images for the project https://packagecloud.io/haf/oss which I think it would be great to have more feedback around - e.g. by having the core eventstore team work with the recipe to make it fully featured (upgradable, auto-run
upgrade scripts, proper configuration) and to make it work well with puppet and/or other configuration management tools.
Similarly to feeds of OSS, I think blessed packages for config management tools would fall inside the realm of the commercial product.
I think that having a gitter chat room would be an improvement too
https://gitter.im/EventStore
I set one up by mistake (now deleted) and was underwhelmed. The mailing list seems to me a much better place for discussions since it relies less on real-time communication (which is practically impossible anyway given that the entire team are in different
time zones).
Removing the dual vocabulary; what’s commercial, what’s open source - and being much more specific about what options can be purchased from you at a premium and which ones can’t.
I agree there needs to be a much clearer picture about what is commercial vs open source and what we will therefore never support or merge into the open source product regardless of contributions. I’ll open up an internal discussion about this.
Cheers,
James