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

How do you run the server? #86

Open
PEZ opened this issue Oct 15, 2019 · 3 comments · May be fixed by #87
Open

How do you run the server? #86

PEZ opened this issue Oct 15, 2019 · 3 comments · May be fixed by #87

Comments

@PEZ
Copy link

PEZ commented Oct 15, 2019

Hello,

I can't figure out how to build this in a way that I later can run it. This is my first Rust thing ever. I have installed rustup and it got me cargo. I have run cargo build and it compiles everything, even if there are some deprecation warnings.

Running cargo run gives me:

a bin target must be available for `cargo run`

I've also tried cargo build --all-targets and the tests got my machine really hot, but still the same cargo run results.

I checked the video presentation linked in the README and saw the command cargo run --bin server -- -- used, but it gives me:

error: no bin target named `server`

I also looked at the Travis file and did the clippy things (w/o having the faintest idea about what I am doing), but same results.

Now I am out of ideas, and love me some clues.

@comnik
Copy link
Owner

comnik commented Oct 15, 2019

Hi,

I have installed rustup and it got me cargo. I have run cargo build and it compiles everything, even if there are some deprecation warnings.

So far, so good!

a bin target must be available for cargo run

Cargo differentiates between libraries and binaries. Declarative-dataflow (the main directory) contains only the library. Check out the server/ directory for the server binary. If you run cargo run within that subdirectory, you should be able to run the binary.

Clippy is a tool that checks our code for common issues / style problems. It's not required for the build to work.

Good luck!

PEZ added a commit to PEZ/declarative-dataflow that referenced this issue Oct 15, 2019
Fixes comnik#86 

Not at all sure you want this info here. 😄

If the info is appropriate, then maybe also inform about which port it starts listening to. (Something I think should be showing in the ”Server running” message.)
@PEZ
Copy link
Author

PEZ commented Oct 15, 2019

Yes, that worked. Thanks!

I proposed an addition about this to the README. Maybe more non-rustians (or whatever you call yourselves 😄) would benefit from that.

@PEZ PEZ linked a pull request Oct 15, 2019 that will close this issue
@PEZ
Copy link
Author

PEZ commented Oct 15, 2019

OK. So hadn't created the PR. Now I have proposed the add. 😏

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 a pull request may close this issue.

2 participants