-
Notifications
You must be signed in to change notification settings - Fork 303
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
Self-installing version of KA Lite #1653
Comments
I like the high-level idea of a self-installing version (one that runs Question: How would it know the difference between being run manually (when it's ok to ask questions) and via, say, a cron/init.d job (when it should run with no input)? Suggestion: This would dovetail nicely with shifting more of this config process into the browser, in the manner suggested by #1835. |
In the code there's a couple of ways it does this:
From |
Cool, sounds good. Looking through the code now. Not pushing on it here (since it looks like we have what we need for a Nalanda MVP), but longer-term, I see many advantages to shifting all setup involving user-input into the browser. Two big advantages:
Do we have any issues about moving in that direction, or should I open one? |
I agree. Only related issue I'm aware is the one you just opened :) |
@jamalex have you tested / verified that the old functionality referenced above works? And is |
@jamalex your update here would be greatly appreciated! Our goal is to complete RCT1 KA Lite-related issues by April 15. Thanks! |
Verified that the existing code works. Just add @jamalex no need to update. |
Now that we have the
kaserve
command, we are in the codepath of server start--before the main KA Lite code is really started.We can have a self-installing version of KA Lite; lots of possibilities exist:
setup
command directly fromkaserve
, if neededlocal_settings.py
... or don't create one.The text was updated successfully, but these errors were encountered: