Jon Bake

This should be relatively easy to implement. The buttons are currently rendered as a [CSS pseudo element](https://github.com/jonmbake/react-terminal-ui/blob/v0.2.1/src/style.css#L33). We'd have to change them to something like a HTML button element instead...

[Terminal width is set to 100% by default](https://github.com/jonmbake/react-terminal-ui/blob/master/src/style.css#L9). Is the issue only with the height? (Height is set to [600px by default](https://github.com/jonmbake/react-terminal-ui/blob/master/src/style.css#L22)).

Thanks for opening this issue, @MeyerBuaharon . Feel free to open a PR if you have a fix!

I am not super familar with Discourse's "invite only" mode. It seems like it is set at the user group level. Is that correct? The plugin does allow specify user...

I haven't seen that error before. Can you check the Discourse log and provide the stack trace?

@Paradoxcron I'm not sure of cause. I'm assuming there was a breaking API change in Discourse 3.2.0. Are there any contributors to this project that may have time to due...

Hmm... This appears to be a caused by a change in discourse. In the past, the folder name did not have to match the plugin name. Not finding an issue...

@ziima In the previous Discourse versions, Discourse would create the User account if an auth plugin returned a valid authentication result and the user account did not exist. It's weird...

@davidtaylorhq Any ideas why user creation would fail after a successful auth here? Did anything change with `Auth::Result`?

Hey @mhamiltonj . > how to configure the `ldap lookup users by` setting This controls how [the lookup of the Discourse user after authentication will be done](https://github.com/jonmbake/discourse-ldap-auth/blob/eca02c560f2f2bf42feeb1923bc17e074f16b891/lib/ldap_user.rb#L8). Setting it to...