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

Cut over to [email protected] #202

Closed
6 tasks done
thedodd opened this issue Jul 28, 2021 · 0 comments · Fixed by #211
Closed
6 tasks done

Cut over to [email protected] #202

thedodd opened this issue Jul 28, 2021 · 0 comments · Fixed by #211
Labels
enhancement New feature or request

Comments

@thedodd
Copy link
Member

thedodd commented Jul 28, 2021

Objectives

  • cut everything over to Tokio.
  • don't use futures sync/channel primitives, use Tokio's.
  • cut over to hyper + routerify for server, proxy & websockets.
  • test: setup an example which demo's the use of Trunk's proxy system (standard http & websockets). This could be used for CI testing as well, as the binary could be built and used for the test, and then a demo backend could just echo data.
@thedodd thedodd added the enhancement New feature or request label Jul 28, 2021
This was referenced Jul 30, 2021
thedodd added a commit that referenced this issue Aug 4, 2021
Cut over to [email protected]. Much more simple interface, and works
quite nicely with the async ecosystem.

Cut over to axum for web server. Much better!

The updated server stack is now more intelligently handling 404s. This
is a common issue where users may end up making a request for some
non-html static asset, but they get their path slightly wrong and are
served the index.html instead of a 404.

This typically results in users struggling to find the problem, and
often times users have opened issues in GH. This updated algorithm will
now evaluate 404s more closely and only respond with the index.html when
the `accept` header allows for text/html or */*.

Added an example demonstrating all proxy functionality.

closes #198
closes #202
closes #209
thedodd added a commit that referenced this issue Aug 4, 2021
Cut over to [email protected]. Much more simple interface, and works
quite nicely with the async ecosystem.

Cut over to axum for web server. Much better!

The updated server stack is now more intelligently handling 404s. This
is a common issue where users may end up making a request for some
non-html static asset, but they get their path slightly wrong and are
served the index.html instead of a 404.

This typically results in users struggling to find the problem, and
often times users have opened issues in GH. This updated algorithm will
now evaluate 404s more closely and only respond with the index.html when
the `accept` header allows for text/html or */*.

Added an example demonstrating all proxy functionality.

closes #198
closes #202
closes #209
thedodd added a commit that referenced this issue Aug 5, 2021
Cut over to [email protected]. Much more simple interface, and works
quite nicely with the async ecosystem.

Cut over to axum for web server. Much better!

The updated server stack is now more intelligently handling 404s. This
is a common issue where users may end up making a request for some
non-html static asset, but they get their path slightly wrong and are
served the index.html instead of a 404.

This typically results in users struggling to find the problem, and
often times users have opened issues in GH. This updated algorithm will
now evaluate 404s more closely and only respond with the index.html when
the `accept` header allows for text/html or */*.

Added an example demonstrating all proxy functionality.

closes #198
closes #202
closes #209
thedodd added a commit that referenced this issue Aug 5, 2021
Cut over to [email protected]. Much more simple interface, and works
quite nicely with the async ecosystem.

Cut over to axum for web server. Much better!

The updated server stack is now more intelligently handling 404s. This
is a common issue where users may end up making a request for some
non-html static asset, but they get their path slightly wrong and are
served the index.html instead of a 404.

This typically results in users struggling to find the problem, and
often times users have opened issues in GH. This updated algorithm will
now evaluate 404s more closely and only respond with the index.html when
the `accept` header allows for text/html or */*.

Added an example demonstrating all proxy functionality.

closes #198
closes #202
closes #209
thedodd added a commit that referenced this issue Aug 5, 2021
Cut over to [email protected]. Much more simple interface, and works
quite nicely with the async ecosystem.

Cut over to axum for web server. Much better!

The updated server stack is now more intelligently handling 404s. This
is a common issue where users may end up making a request for some
non-html static asset, but they get their path slightly wrong and are
served the index.html instead of a 404.

This typically results in users struggling to find the problem, and
often times users have opened issues in GH. This updated algorithm will
now evaluate 404s more closely and only respond with the index.html when
the `accept` header allows for text/html or */*.

Added an example demonstrating all proxy functionality.

closes #198
closes #202
closes #209
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant