Skip to content
This repository was archived by the owner on Jun 22, 2025. It is now read-only.

Conversation

@samuelhwilliams
Copy link
Collaborator

This will allow end users to create their own Bottle app and inject any
middleware they want, e.g. to handle authentication or session
management, before Eel takes over.

Resolves #199

This will allow end users to create their own Bottle app and inject any
middleware they want, e.g. to handle authentication or session
management, before Eel takes over.

Resolves #199
@samuelhwilliams samuelhwilliams marked this pull request as ready for review October 22, 2019 17:05
@samuelhwilliams samuelhwilliams merged commit e6f4328 into master Oct 22, 2019
@samuelhwilliams samuelhwilliams deleted the app-start-arg branch October 22, 2019 17:06
samuelhwilliams added a commit that referenced this pull request Nov 18, 2019
PR #203 added the ability for users to pass a custom Bottle instance to
Eel, which was intended to help them add middleware. Unfortunately, the
custom app instance has no routing set up and so fundamentally fails to
support Eel's functionality.

This patch applies the functions that handle routing to any custom
bottles before handing off off to bottle to run the server.

Fix #211
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Passing a bottle app instance to eel

2 participants