conduit-rust / conduit Goto Github PK
View Code? Open in Web Editor NEWWeb Application Interface for Rust
License: MIT License
Web Application Interface for Rust
License: MIT License
It would be nice to have at least a "Hello World" example.
An old version of conduit
has dependencies specified with "*"
version requirement (semver = "*"
).
Crates with such vague dependency versions became unusable, because *
allows picking too-new semver-incompatible dependencies.
It also breaks Cargo's minimal-versions
feature, because *
requirement allows picking very very old dependencies that aren't compatible with Rust 1.0.
Because this old version of conduit
is unusable and may cause problems for Cargo, I suggest yanking it:
cargo yank --vers 0.5.0
Is there any feature of conduit to receive formdata request?
I'm confused as to why this exists.
I have recently been investigating various rust web frameworks and found this one. I know it is in use in hosting the crates.io repository, and was hoping it would be useful for my needs as well.
However it appears to be lacking any form of documentation currently, I was wondering if this was something the project wanted? If so I would be willing to try to help out with this.
When working on conduit you currently have to clone what feels like a dozen different repositories, and similarly you need to have all of them open in your editor.
I'm wondering if it would be easier to import all of these other conduit-XXX crates into a shared Cargo workspace in this repository.
If there is any interest in this I would be happy to work on that.
This issue was automatically generated. Feel free to close without ceremony if
you do not agree with re-licensing or if it is not possible for other reasons.
Respond to @cmr with any questions or concerns, or pop over to
#rust-offtopic
on IRC to discuss.
You're receiving this because someone (perhaps the project maintainer)
published a crates.io package with the license as "MIT" xor "Apache-2.0" and
the repository field pointing here.
TL;DR the Rust ecosystem is largely Apache-2.0. Being available under that
license is good for interoperation. The MIT license as an add-on can be nice
for GPLv2 projects to use your code.
The MIT license requires reproducing countless copies of the same copyright
header with different names in the copyright field, for every MIT library in
use. The Apache license does not have this drawback. However, this is not the
primary motivation for me creating these issues. The Apache license also has
protections from patent trolls and an explicit contribution licensing clause.
However, the Apache license is incompatible with GPLv2. This is why Rust is
dual-licensed as MIT/Apache (the "primary" license being Apache, MIT only for
GPLv2 compat), and doing so would be wise for this project. This also makes
this crate suitable for inclusion and unrestricted sharing in the Rust
standard distribution and other projects using dual MIT/Apache, such as my
personal ulterior motive, the Robigalia project.
Some ask, "Does this really apply to binary redistributions? Does MIT really
require reproducing the whole thing?" I'm not a lawyer, and I can't give legal
advice, but some Google Android apps include open source attributions using
this interpretation. Others also agree with
it.
But, again, the copyright notice redistribution is not the primary motivation
for the dual-licensing. It's stronger protections to licensees and better
interoperation with the wider Rust ecosystem.
To do this, get explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright) and then add the following to
your README:
## License
Licensed under either of
* Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
* MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
at your option.
### Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.
and in your license headers, use the following boilerplate (based on that used in Rust):
// Copyright (c) 2016 conduit developers
//
// Licensed under the Apache License, Version 2.0
// <LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0> or the MIT
// license <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
// option. All files in the project carrying such notice may not be copied,
// modified, or distributed except according to those terms.
Be sure to add the relevant LICENSE-{MIT,APACHE}
files. You can copy these
from the Rust repo for a plain-text
version.
And don't forget to update the license
metadata in your Cargo.toml
to:
license = "MIT/Apache-2.0"
I'll be going through projects which agree to be relicensed and have approval
by the necessary contributors and doing this changes, so feel free to leave
the heavy lifting to me!
To agree to relicensing, comment with :
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
Or, if you're a contributor, you can check the box in this repo next to your
name. My scripts will pick this exact phrase up and check your checkbox, but
I'll come through and manually review this issue later as well.
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
These updates are awaiting their schedule. Click on a checkbox to get an update now.
These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.
conduit-conditional-get/Cargo.toml
time 0.2
conduit-middleware/Cargo.toml
conduit-router/Cargo.toml
route-recognizer 0.3
thiserror 1.0.38
tracing 0.1.37
lazy_static 1.4.0
tracing-subscriber 0.3.16
conduit-static/Cargo.toml
conduit-mime-types 0.8
time 0.2
filetime 0.2
tempdir 0.3
conduit-test/Cargo.toml
conduit/Cargo.toml
http 0.2
.github/workflows/ci.yml
actions/checkout v3
Swatinem/rust-cache v2.2.0
actions/checkout v3
Swatinem/rust-cache v2.2.0
actions/checkout v3
Swatinem/rust-cache v2.2.0
actions/checkout v3
Swatinem/rust-cache v2.2.0
As requested by @wycats on IRC, here are some of my thoughts on what conduit should change/adapt so that it can be a stable standard for Rust web development:
Primarily Conduit needs to decide whether it is a "raw" specification for relatively low-level HTTP implementations or a high level specification for full web applications to use directly.
&'static str
is problematic, since incoming requests will always produce non-'static strings.Url
struct instead of scheme
, host
, virtual_root
, path
, and query_string
.Show
.phrase()
method.I'm not sure what the future of conduit is. It's entirely possible that it could develop a really nice high level interface and be used by all higher level frameworks - however, it's also possible that it could tie itself to a complex interface which frameworks decide they don't want all of and that could further fragment Rust web dev.
If you're not at all attached to the "conduit" name, you might leave it reserved for a port somebody might someday do of haskell's "conduit" library:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.