-
Notifications
You must be signed in to change notification settings - Fork 30
FastAPI port of API/Studio, second time around #360
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
Changes from 16 commits
1fe3385
74e6172
605ccd3
1bba827
5922f6f
98a07f1
89bd9b3
cfc50c6
ebc16ff
0a7c78b
4bcd948
bd33314
f4683a9
d5d2086
f55e6bb
9bc3855
ff6c92d
2d68577
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
web: gunicorn --worker-class eventlet -w 1 g2p.app:APP --no-sendfile | ||
web: gunicorn --worker-class uvicorn.workers.UvicornWorker -w 1 g2p.app:APP |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -100,22 +100,14 @@ been using them and should not be construed as public API documentation. | |
|
||
## Some CLI commands no longer exist | ||
|
||
Several commands for the `g2p` command-line have been removed as they | ||
were duplicates of other functionality: | ||
Several commands for the `g2p` command-line have been removed: | ||
|
||
- run | ||
- routes | ||
- shell | ||
|
||
To run the `g2p` API server, you can use: | ||
|
||
flask --app g2p.app run | ||
|
||
Likewise, for `routes` and `shell`, you can use: | ||
|
||
flask --app g2p.app routes | ||
flask --app g2p.app shell | ||
|
||
To run G2P Studio, use: | ||
To run the `g2p` API server and G2P Studio, you can use: | ||
|
||
python run_studio.py | ||
|
||
It does not seem that any equivalents of `routes` or `shell` exist. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here this is conflating the migration from 1.x to 2.0 and from 2.0 to what will probably have to be 2.1 or possibly even 3.0 if this is not backwards compatible. While I don't think we need a separate migrating to 2.1 file, I think this section should distinguish between migrating to 2.0 (previous text) and to 2.1 new text like you're writing here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. well, there's the auto-generated online API documentation, which is arguably more useful anyway... |
Uh oh!
There was an error while loading. Please reload this page.