Skip to content
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

Move dns challenge as an additional binary for foxbox (Closes #423, #… #440

Closed

Conversation

julienw
Copy link
Contributor

@julienw julienw commented Apr 27, 2016

…424)

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 664d68b on julienw:423-424-build-dnschallenge-from-foxbox into * on fxbox:master*.

@julienw julienw force-pushed the 423-424-build-dnschallenge-from-foxbox branch from 664d68b to 34346d4 Compare April 28, 2016 15:08
@julienw
Copy link
Contributor Author

julienw commented Apr 28, 2016

@fabricedesre @JohanLorenzo @samgiles what do you think ?

@samgiles
Copy link
Contributor

It works for me!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 38.441% when pulling 34346d4 on julienw:423-424-build-dnschallenge-from-foxbox into b08ff2c on fxbox:master.

@@ -143,17 +143,20 @@ There are several command line options to start the daemon:
Currently you would likely want to start the daemon like this:

```bash
cargo run -- -r http://knilxof.org:4242 --disable-tls
./run.sh -- -r http://knilxof.org:4242 --disable-tls
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not need the extra --

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I discussed with @JohanLorenzo and we decided to keep it especially to be able to use cargo's --verbose.

We could special-case this but this is more work.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed that with @julienw, we thought -- still has some value, when you want to --verbose or --freatures on cargo, for instance.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But then your run.sh script adds very little over the cargo command...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it's merely an alias to make things easier for the developer now that we have several binaries.

Totally open to rework this though :)

@fabricedesre
Copy link
Collaborator

I'm fine with the approach, but there are a few things to address.

@JohanLorenzo
Copy link
Contributor

Looks good to me

@julienw
Copy link
Contributor Author

julienw commented Apr 28, 2016

I pushed the small typo change.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 38.441% when pulling 0d1ed07 on julienw:423-424-build-dnschallenge-from-foxbox into b08ff2c on fxbox:master.

@julienw julienw force-pushed the 423-424-build-dnschallenge-from-foxbox branch from 0d1ed07 to 6825f2e Compare April 28, 2016 17:50
@julienw
Copy link
Contributor Author

julienw commented Apr 28, 2016

landed in ecc92fa

@julienw julienw closed this Apr 28, 2016
@coveralls
Copy link

Coverage Status

Coverage remained the same at 38.441% when pulling 6825f2e on julienw:423-424-build-dnschallenge-from-foxbox into e42e681 on fxbox:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants