-
Notifications
You must be signed in to change notification settings - Fork 38
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
Kitchen Site is down #439
Comments
site down again? Any word on the distributed exe being updated to the current version so we can have a backup? |
Site down again. :-( |
|
Site down again! Could you please address this conclusively? Thanks. |
Hi Petar!
Really love MK. Happy to support you in any way. |
Hi all, Site is up and running (I didn't touch it - no idea why it looks down to you). @Extra-Extra-Dev answers:
Sorry for "no idea" answers :P |
HAHAHAHa well.. I think I speak for everyone in thanking you for everyone and the response. I admit .. . due to my own bad work habits, I'm often on here on Friday nights (EU time) and it goes down often. Maybe it's a faulty observation! As for the site.... it's been faster for me when it's up. Like very! Weird. *Combined, I think your fans are curious your hosting environ. Maybe the collective knowledge can help with the outages esp if you've not touched it. Version differences... yes. I believe the "version issue" is that the command line is 0.9.107 yet the MK UI from GIT at https://github.com/perak/kitchen-site is not touched in 2 years. I think I may speak for others in assuming the could not possibly be compatible (and in my case didn't research!). But I believe thats the backup others are seeking for offline authoring and compiling. Any clarity there is appreciated. I have some UI/authoring ideas for you too. When I feel I'm in sync with you I'd love to contribute back! |
I had brute force attacks on site for a long time, and my suspect was that it causes blackouts. No idea who and why were brute-forceing my server, but it took more than a year. Looks like now attacks stopped (that could be reason it is faster), but outages continues. I was investigating, and dig all possible log files, but nothing which tells me why it dies. Looks like there is dead loop somewhere - during outages nodejs eats 100% CPU. What I suspect is that someone's project has self-reference or something and when saving a document, server re-parses json (maybe I can skip this re-parseing...) and enters into dead loop. Second suspect could be bug in some of zillion nodejs modules included into project. But this is hard to debug. It never happened locally - happens only in production. Fixing this bug is time consuming, and this project is not priority for me. I wish to fix it and release you guys from pain, but I'm not sure when I will do it - cannot promise anything. |
It's down again. I've built a pretty sweet app using your site. I'd like to contribute-in some feature ideas regarding: connection overrides, non-reactive sources, a few bug fixes, some UI enhancements (editor view, expandable panes). |
@Extra-Extra-Dev it self-healed! :o (that's art of coding! :D ) So, possibly |
Site down more than 24 hours. Sad panda. |
oh oops. and now back.. .Maybe talking about it woke it up ;-) |
Hi, the site is down.
I asked this before, but it would probably be hugely helpful if the kitchen tool could be made available as an install vs. cloud only.
Thanks!
Oliver
The text was updated successfully, but these errors were encountered: