-
Notifications
You must be signed in to change notification settings - Fork 192
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
Docs: update REST API wsgi scripts #4488
Docs: update REST API wsgi scripts #4488
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4488 +/- ##
===========================================
+ Coverage 79.31% 79.32% +0.01%
===========================================
Files 475 475
Lines 34840 34840
===========================================
+ Hits 27630 27632 +2
+ Misses 7210 7208 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
aee8235
to
00d3bfa
Compare
The wsgi scripts for deploying the AiiDA REST in production were outdated and are updated. The how-to on deploying your own REST API server is significantly streamlined and now includes the wsgi files as well as the examplary apache virtualhost configuration.
00d3bfa
to
5012235
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
About your question: My guess is that he had actually tested it - but it's also true that it was a very old version of AiiDA so not even sure if this still works. |
I didn't really know what the difference was, so I wasn't sure. I've now had a quick look and I think it wouldn't really make a difference - even WSGI applications running inside the same process (group) will run in separate sub interpreters and thus lead to (practically) the same memory consumption. There is, however, also the application group directive which lets wsgi applications run inside the same interpreter. |
fixes #4030
Open questions: