holy crap that was rough...I guess compared to some other things it's not so bad, just gets a little ambiguious with those two seperate pieces and the lack of documentation..it's not really complicated, just takes a bit if u have no idea what you're doing
@kellyelton How do you feel that we can make the setup easier? I get having a step by step install doc in the repo is needed as well as a video but anything else?
@kellyelton@ejsmith, I'm under the assumption from some recent support cases that people expect us to list how to install everything (mongo, elastic, redis) and even configure acls on azure.. I think this is outside the scope of what we provide but we should make it easy to find those install docs for (mongo, elastic, redis), docker images would help. What are your thoughts. We want to make setup a breeze
From me experience with self-hosting Exceptionless, the most problems isn't with installation additional applications (Elasticsearch, Mongo, Redis, etc.) , but I had problems with correctly setting IIS, hosting API and UI in difference folders and URLs, setting OAuth, changes for send notifications emails, etc. Generally , now in .NET you can use PowerShell (WintellectPowerShell, Psake), MSBuild or maybe Fake - I use it in my projects, because is possible run it on Mono.
I need add machine key, change URLs , remove URL rewrite in UI web.config, change settings to SMTP... and of course I must change permission to applications pool. I think that configuration on IIS is always problematic, sometimes difficault, and maybe better will be creating self-hosted with Owin ?
Now, I have problem with send emails. Now I have problem with correctly create URL to verify an user inside in mail.
It seems like setting up mongo redis and elastic search wasn't so bad
the parts that threw me for a loop was a) I assumed the Exceptionless repo was the only front facing piece, didn't realize until later that Exceptionless.UI was the interface. The backends 'Login' link linked to your guyses hosted service, so I assumed after that that the front end was hosted and somehow did api calls back to my back end b) SSL requirements(UI forces ssl for example) c) the usage of BASE_URL being ambiguous
A really did a huge number on me honestly
I also thinkt hat in the client docs there are certain places (I wish I could quote off the top of my head here) where there was no mention of how you configure it for hosted, which was slightly different
As well as no possible idea(outside of being lucky that I saw it in chat here) how authentication worked and how to set it up