matthewfl
Hosting offline version - requires login & fails
When I'm running this locally, when I try to save it asks for a login. At which point I can't create a new user or login (not that I've set any user details).
When I try to create new user, it redirects to localhost:8080/newUser - which is the result of static/newUserName.html - which then keeps redirecting on submit without any notice of what it's doing. I tried logging in with the credentials I gave the "newUser" page, but those fail too.
Any pointers?
I do not quite understand what you mean by it asking for a login when you try to save, as this is expected.
As for not being able to login with the new login you are making. It is attempting to redirect to the home page, or to the "username all ready taken" page.
I would check the database to make sure that your login info is there as it should be. It should be contained in a login_username key, and the value will be a hash of your password.
Sorry, I didn't mean that it was unexpected that I needed to login - only that registering and trying to login would fail consistently.
I couldn't find any directions on the database or login_username. I've just started poking around the config.js and changing some of the properties there. I've also found a file called database.db - which is consistently empty.
No matter what I put in the lightbox when registering a new user, it always redirects me to the /newUser page.
I'm also stuck at this point. I'm guessing tyrant is the default DB but how am I suppose to check it out? Since remy comment is one year old, seems like matthewfl is out of time. I really like node-host and I'm willing to help develop it, please don't let this project die.
My issue is that I have never been able to replicate this issue and can only assume that it is an issue with configuration of tyrant or node-host (of which I am not sure).
The only thing that I can think of is that you might not have properly linked the db.tyrant.js file to db.js, but not doing so should cause an error with node and be unable to start. However on that node, you could link the db.nstore.js file rather than the db.tyrant.js and you should be able to use nstore, but I don't guarantee the stability of that or that you will even have better luck than with tyrant.
Additionally as you have guess I am "out of time"