A middleware to responde in json: https://github.com/sunng87/iron-json-response

Maybe it is an idea to showlist the features of the packages. That way you can check if what you need is already there or not. Just like the comment below

https://github.com/GildedHonour/frank_jwt -- json web token

Canten is a micro web framework inspired by Python's Flask.

https://gitlab.com/jeffdn/rust-canteen

Not sure where we could talk about it, but the PoC implementation of an HTTP server using futures (zero-cost futures) seems important for rust and web:
https://github.com/alexcrichton/futures-rs/tree/master/futures-minihttp

Should we mention it?

https://github.com/diesel-rs/diesel/releases/tag/v0.10.0

This is a fairly big deal as far as how 'web' rust is, I think

edit: I mean like, properly on stable not using the syntex stuff.

References:

• https://crates.io/crates/horrorshow
• https://stebalien.github.io/horrorshow-rs/horrorshow/
• https://crates.io/crates/horrorshow https://github.com/Stebalien/horrorshow-rs

/cc @Stebalien

Due: July/August maybe?

Items (please add and I update the topic):

New Crates:

• horrorshow (0.5.5): a templating library written in rust macros

Repo: https://github.com/messense/robotparser-rs
Crates.io: https://crates.io/crates/robotparser

https://github.com/wireapp/proteus

Hi,
it's still in an early stage, but the basic functions of my wrapper for Googles libphonenumber (part of Googles internationalization efforts and very well maintained) already work fine.
You can find the crate here: libphonenumber-sys
It's something that we were missing dearly in our backend and I'm sure other web-related services built with rust have the same need.
Of course it would be great to properly port of the library to rust, but in the meantime this crate should be able to do the work.

Yann

We seem to have a lot of those, adding: https://github.com/softprops/hubcaps

Might want to split out "Github" as a subtopic on "services".

Hi I'm Blake I want to help out as a Curator!

Who I am:
I'm a Python/Swift developer during the day. I found Rust through some close friends in the Python community, we were doing geospatial Python systems and thought Rust was a good language for the geo scene because of its high processing and parallelism. We started GeoRust, an org around geographical formats and libraries. Wanting to further my usage of Rust, I found AWWY back around the Rust 1.0 release. Then a few days ago I saw the news about AWWY.org and spent a good majority of the day reading the updates to the site. It was definitely a call to action for me. I want to be a curator to A) be a more informed community member and B) Give back to a community that has supported me so much already.

I hope this application is sufficient and you will allow me to serve BashyHQ, Rust, and AWWY for years to come.

From this thread, reported by @steveklabnik, there seems to be a bug with the fonts on linux:

hmmm no errors in the console

Iceweasel 38.6.0, debian x86_64.
I don't use blockers. And it's odd because the main site works just fine.

"Tera is a template engine based on Jinja2 and the Django template language."

See https://github.com/Keats/tera for more.

The rust-web-ecosystem is changing quickly and keeping up with the pace is hard. Like just 4 days ago, diesel release version 0.5.0 – a major milestone adding sqlite3 support. This is a big deal and important progress. As the website tracking the progress of the rust-web ecosystem, I think we should relay and emphasize news like this.

This ticket is to discuss on how we might achieve that.

can't we add Sapper for Web Development Frameworks section on arewewebyet.org?

Already earlier I had the idea of having some (semi)-regular Updates of the Rust-Web Ecosystem packed into an ongoing Blogpost series: I called it RustWeb Digest (open for discussion, if you have a better name) and almost a month after starting the relaunch, I think it is time we can compile our first edition. I am thinking of splitting the one into three major parts:

1. Important News and Developments
   The few most important headlines of the ecosystem since the last edition (up to three maybe?), each with a short paragraph summarizing what is going on and why its important – of course linked to the specific items on the web.
2. Further Headlines
   Other internal and external headlines that made the round and might be of interest. This time only the headline and the link though
3. New Package Releases
   Packages we added to the list or which updated their version – big updates might still be mentioned in the sections before, too.

If this sounds good to you, @bashyHQ/awwy-curators I'd like to start compiling content: just post it here.

Example: http://www.arewewebyet.org/news/2015/11/29/announcing-diesel-a-safe-extensible-orm-and-query-builder-for-rust/

The link attributes are quoted like href="\"http://...\"", which results in targets like the following:
http://www.arewewebyet.org/%22https://crates.io/crates/diesel/%22

The web is weird. So there is this library, Neon, or building framework, I guess, which allows you to easily combine Rust and NodeJS, making them work together. As NodeJS doesn't get more "web" (JS and in the Backend) arguably, this is something we should cover on arewewebyet.org . But how exactly? Maybe similarly as we also cover servo? It's weird.

I would suggest adding rustls to the TLS Crypto section.

I believe it satisfies the current statement:

Still missing: a memory-safe TLS lib built in rust only

Thanks for the site. [https://github.com/bashyHQ/arewewebyet/blob/gh-pages/_layouts/frame.html#L63](This line) updates the site with the current date, but I had to dig through the source code to find it. I'm sure people who are looking for a last-updated date don't all want to do that. Could you please put 'Last Updated' somewhere around there. This would reassure people that they're getting up to date advice.

Hey,

I was wondering, now that we have the website up, people realise you can already build stuff with rust for the web and I'd like to foster that attitude. Yet, if you google for it, there isn't much coming up, so I was thinking, it might be cool if we added a Getting Started and/or Examples reading list. Just a Link-Collection if you want, but to give people pointers.

What do you think, @bashyHQ/awwy-curators ?

Category: Web Utils

Links:
https://github.com/cybergeek94/multipart
https://crates.io/crates/multipart

Short description:

Client- and server-side abstractions for HTTP file uploads (POST requests with Content-Type: multipart/form-data). Supports several different HTTP crates, including Hyper and Iron.

License: MIT/Apache 2.0 dual-license

We are waiting for the following to reach maturity to be released on crates.io:
hyper-tokio a tokio/futures based hyper

Hyper is on crates now.

The symbols used to indicate stability and maturity are explained on

http://www.arewewebyet.org/about/ under the Understanding the level indicator section.

But it would be better if their meaning was more readily available on the front page (or throughout the site). Here are some suggestions:

• A fixed view (a div perhaps) with the legend that is always available when navigating the site
• Displaying the meaning of the symbol on hover anywhere it is displayed
• A simpler level indicator code that is easier to understand without the need for explanation. Like just colors ranging from red to green. But not too many of them, maybe just
  • Red: Not stable
  • Yellow: Stable, but immature
  • Green: Stable and ready for production

Anyways, thanks for curating the site. I use it often to check that status of Rust for web dev.

I want to give the website a complete makeover. Among other things I'd like to:

• adapt design from rust-lang.org: colors, fonts, etc – to give it more of the same-family-style
• drop table layout: the content is very inaccessible right now
• restructure content: I am thinking of restructuring the server/client-differentiation into more specific parts, maybe adding a table of contents
• redo into markdown: the table-layout in html is ... not really nice to contribute to, I'd rather have this in simplified markdown
• add comments/reviews per packaged
• small indicator giving insight into the specific topic.
• add news
• feature curators
• explain features of the website
• proper review
• relaunch news bulletin
• add curators

https://rocket.rs

During the review, and as it came up in the other discussion:

I was thinking of also doing that per package – like a comments section by the curators. That would exactly be the place to put such information as you just gave. What do you think, @Manishearth ?

Here is an idea what that could look like:

The color indicates that this is a positive review (green), others could be yellow (warning/attention), red (major blocker/problems), gray or blue (neutral/informational).

I also made a second mockup where it is more to be understood as a quote:

Here is another, shorter version. I am totally in favor of using Unicode-Emoji to indicate positive and negative information quickly, too:

Here is an example that shows this being used for informational purposes with multiple entries:

This shows, how this could quickly become overcrowding if there are a lot of people commenting (which I'd consider a good thing though). In which case I'd suggest to add a toggle button to the top, allowing the viewer to toggle comments on/off: – but that is future talk, if the problem should actually arise.

Question for now is: what do we think about this? Do we have enough reviews/information for this to make sense? How do we like the approach taken?

Most of the links at the start of the page don't point to correct paths, instead point to correct_path + '.html' extension.

The pencil web framework is in a stage that we can (and should) add it to the website: https://fengsp.github.io/blog/2016/3/introducing-pencil/

Hyper do include a client. Since this is mentioned (as "planned") for rotor-http, I think it should be mentioned for hyper.

Hi,

I think this might go well in your logging section:
https://github.com/dpc/slog-rs

see https://crates.io/crates/zip – very stable and mature, should be in the compression topic.

CLI client: https://github.com/onur/letsencrypt-rs
Crate: https://docs.rs/acme-client

Is a pretty big thing in web dev, perhaps adding an entry for that will wake some interest?

Title basically says it all.

@frewsxcv asked at #1:

Can I request https://github.com/briansmith/ring get added to the "crypto" section?

ring is a crypto library in Rust based on BoringSSL's crypto primitive implementations.

With the rewrite ( #1) we are no leveraging much more external data to give as an idea of how good the ecosystem looks. However, as @Manishearth brought up we might still have our own opinion about the stability of certain frameworks, independent from their crates.io-version numbers.

I propose we might want to highlight certain libs as long-time-stable and reliable, while also spotlight some that are new and upcoming, edgy and interesting.

You might consider adding the flexi_logger to the logger list at http://www.arewewebyet.org/topics/logging/

Will be like Nginx/Apache/NodeJS, a reverse proxy all in Rust

https://github.com/sozu-proxy/sozu

Here it is https://github.com/GildedHonour/atarashii_imap

repo
crates.io

Under the RSS section, my feedreader library has been rewritten and is now called feed

Hey,

I've been pondering, if I wanted to do some (rust) web development and I ran into some issues, where would I post/ask about them? I feel the rust-lang forums aren't really the right place for it (but maybe that is just me?), so where? reddit/r/rust? stack overflow? If there is a prominent place, should we point people to it? Or if there isn't, should we provide one? Either through reddit (yikes) or maybe a self-hosted flarum instance – community.arewewebyet.org?

@bashyHQ/awwy-curators what do you think?

first worker queue!!! https://crates.io/crates/oppgave

Zstd-rs is a binding to zstd, which include nice features for web-service, like custom dictionaries to efficiently compress individual small packets.

https://github.com/tomaka/rouille

Writing asynchronous web applications in Rust is not straightforward at the moment. The low level parts are ready (mio, hyper) but a bit of glue is needed to make it more accessible.

Having a section dedicated to asynchronous web development may raise the attention of the Rust community on this matter.