-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation #1
Comments
Can you give a config.json example firstly? Thanks |
There is no config.json. |
Thanks. |
@goldcode88 can you read over the documentation in the referenced PR and give us some feedback? |
@martin31821 |
@martin31821 @johannwagner I think it's preferable if more details can be provided.
2. Edited:
|
It states exactly the problem with your configuration, which is that you have enabled both authorization ways. I added some documentation for the authorization part of autobahnkreuz, so it should be more clear how the parameters work together. a valid command line which I am using for development is the following: |
@martin31821
The key of problem is
I thinks it's more flexible if authfunc is replaced by |
As you can see here we already invoke the ticket-check-func. Any functions you pass to autobahnkreuz via command line flags are wamp functions. The error you are seeing was fixed in 0.9.2, are you sure you are running the latest version? (i.e. docker Edit: |
@martin31821
|
Please use burrow or the prebuilt docker image. Using go get will get you the wrong dependencies. |
@martin31821
|
you are missing a |
We should consider adding a section to the burrow README that shows how the usual workflow with burrow looks like. I think it is not clear that burrow mimics a npm like workflow. @martin31821 |
|
Your |
@martin31821 @fin-ger
Then I use Anyway, I can continue to try |
Burrow build options are fixed in burrow.yaml, since burrow is designed for creating reproducible builds and docker-based deployments. |
@goldcode88 You can use
to add additional temporary flags to the |
@fin-ger @martin31821 |
User documentation
Developer documentation
Release information
The text was updated successfully, but these errors were encountered: