-
Notifications
You must be signed in to change notification settings - Fork 4
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
Automate setup of LRS, store valid credentials in config.ini #8
Comments
Yes, The credentials in the config.ini must be synced with those of the Learning Locker LRS. There should also be better error reporting in the swagmapviewer, but there is already another issue for that. |
Hrmm... the provisioning system should put appropriate values in there. I can look into it, but not until at least tomorrow, most likely. Too much stuff I have to prioritize at work for today. :( |
...oh, of course, those vars are just using default values right now. We won't be able to put real values in until we've automated setting up an LRS in LL. |
Ok, I took the time to create an LRS and put proper credentials into config.ini and now it works! I'll re-title this issue to deal with automating the setup. |
So currently we are populating MongoDB with data that we thing should be In that case I can look into it...
|
Here's something to start with: I made a list of the files in the LL dir and in /var before and after creating the LRS. It looks like it does do something to mongo, but I've found no evidence of the LRS data actually going there, so it might be some other incidental thing. Those Good hunting! ;)
|
...actually, now there is an |
Ok! Will first also see if I maybe can create a Laravel module to install inside LearningLocker that calls the actual methods inside LearningLocker to set up an LRS. Might not be that much more work... Will see if it works on the first try... :) |
...actually, I gave in and started messing around, and I think I've found what needs to be added to the provisioning system. Stay tuned! |
:)
|
Try pulling |
I pulled usernamenumber/ll_automation and used the Facebook login. I didn’t see the Facebook login at first so I ran vagrant provision again. Then it seemed to work for me .. I see the screen below. Great work guys!! There is no interaction on the page. Is something supposed to happen when I click on the Levels. I’m also still unclear on how to find the files in the VM. What login and password do I use? Thanks, On Wednesday, May 13, 2015 at 10:20 AM, Mikael Lindqvist wrote:
|
@neerajkamdar I don't see a screenshot there. Try editing your post and re-uploading? @limikael Is this what happens when you do |
I did:
Will try with a fresh clone... |
@neerajkamdar Currently that's all that happens, it shows which levels you have completed... Eventually what should happen, is that when you click on a "swagifact" (i.e. here the levels) you should get some information about what you need to do to complete that swagifact and collect the swag... In this case it would say something like:
Or something similar, and then there would be a screenshot and instructions on how to start KTouch. If it would be something web based (such as KALite) it would take you directly to the url where you can do the KALite exercise that gives you the swag... It it is something not web based (like KTouch) there would just be instructions... But all this remains to be done! |
@limikael Hmm.. what you did probably should have worked, but here's hoping. If you do a fresh export, don't forget to create a new localconfig.yml so it uses the swag_dev profile. |
Argh. Just tried this myself with a fresh vm, and now I'm getting the 401 errors as well. :( Will investigate. |
If you try to go to the lrs view page in LL, it crashes, which might give us some clues for what we need to fix. My guess is there's something else that needs to be done in addition to just populating mongo. |
Laravel plugin... :)
|
Nope, as Micke says, that's exactly what you should be seeing. The goal right now is to have an easily-deployable dev environment to make it easier to work on making that better. :) ...only now I'm really confused. If it's working for you, why is it not working for me or Micke?? |
_Update:_ This issue was initially created for what turned out to be a symptom of incomplete configuration. The issue has been re-purposed to track automating those configuration tasks.
My guess is that we have the wrong credentials in swagportal's config.ini, but I don't have time to troubleshoot now, so here's what's going on:
When I try to load the example swagmap it hangs, while the JS console gets 64 messages like this:
Following that url returns the following JSON:
The text was updated successfully, but these errors were encountered: