Claudius Coenen

I did exactly that, though. And it still works. I went from 5.39 straight to 6.1.

In old setups, the port 8000 was used, as seen in the Dockerfile and the config.json: https://github.com/mattermost/mattermost-docker/blob/f394fb1d15b02c7de89f9fe6debbdac740228c75/app/Dockerfile#L54 and https://github.com/mattermost/mattermost-docker/blob/f394fb1d15b02c7de89f9fe6debbdac740228c75/contrib/aws/app/mattermost/config/config.json#L6 When migrating over to this repository, the regular default of 8065...

@dessalines would you still be open to contributions regarding OAuth?

Wouldn't it make more sense to improve Golang's elevation instead of rewriting (and leaving go behind)? Are there other problems besides requesting elevated rights?

I get the same thing. Not sure if this is related in any way.

This does not change if i'm using backslashes instead of forward slashes.

``` ruby Encoding.find('filesystem') # => ``` This is a Windows 7 (x64) machine with this environment: ``` C:\Users\user>bundler env Bundler 1.7.12 Ruby 2.1.5 (2014-11-13 patchlevel 273) [i386-mingw32] Rubygems 2.4.6 ```

`exiftool -j "C:/tmp/2009-03-07 test Path ???/IMG_4224.JPG"` - it seems to replace the umlauts with question marks, which are a wildcard on windows (single character).

The examples earlier were from irb, with no encoding set, explicitly. Here's all of the encoding outputs for reference ``` ruby Encoding.find('external') # Encoding.find('internal') # nil Encoding.find('filesystem') # Encoding.find('locale') #...

it can't find the file, but what i find more interesting is, that the encoding is wonky, so maybe it's already broken before it hits exiftool? I ran these lines:...