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

Self-installing version of KA Lite #1653

Closed
bcipolli opened this issue Mar 1, 2014 · 7 comments
Closed

Self-installing version of KA Lite #1653

bcipolli opened this issue Mar 1, 2014 · 7 comments
Assignees
Milestone

Comments

@bcipolli
Copy link
Contributor

bcipolli commented Mar 1, 2014

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:

  • Launch the setup command directly from kaserve, if needed
  • Put an admin username/password into local_settings.py... or don't create one.
@jamalex
Copy link
Member

jamalex commented Apr 1, 2014

I like the high-level idea of a self-installing version (one that runs setup if needed from within kaserve).

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.

@bcipolli
Copy link
Contributor Author

bcipolli commented Apr 1, 2014

In the code there's a couple of ways it does this:

  • If enough info is passed to the command, it won't ask regardless.
  • You can also pass the --noinput flag, and it will use some useful defaults.

From kaserve, it should always be silent. So all the necessary arguments should be passed. If not available, and the server's not installed, then kaserve should fail.

@jamalex
Copy link
Member

jamalex commented Apr 1, 2014

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:

  • Can be done remotely, e.g. over wifi on a Pi.
  • Has easy access to all the i18n machinery.

Do we have any issues about moving in that direction, or should I open one?

@bcipolli
Copy link
Contributor Author

bcipolli commented Apr 1, 2014

I agree. Only related issue I'm aware is the one you just opened :)

@bcipolli
Copy link
Contributor Author

@jamalex have you tested / verified that the old functionality referenced above works? And is ka-lite in the linux image set up with a local_settings.py to take advantage of this (and in a pre-install state)?

@bcipolli
Copy link
Contributor Author

@jamalex your update here would be greatly appreciated! Our goal is to complete RCT1 KA Lite-related issues by April 15. Thanks!

@bcipolli bcipolli assigned bcipolli and unassigned jamalex Apr 15, 2014
@bcipolli
Copy link
Contributor Author

Verified that the existing code works. Just add INSTALL_ADMIN_USERNAME and INSTALL_ADMIN_PASSWORD, and setup will be run on the first server start via kaserve.

@jamalex no need to update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants