I've made a bot/app in visual studio code and Node JS and it runs fine, but i have other projects I need to relaunch as well while keeping the current one running. I remember having this problem years ago called pm2, thought it was pretty useful, but as i recall the bug problem was while it could relache the app if it crashed so it stayed up 24/7 i didn't have acess to the console log which i use to track the topic that trigers my app, the user name who triggered it and the response. Anyone familiar with PM2 or another program that would retain the console for each running app?
Edit: found some info via
https://pm2.keymetrics.io/docs/usage/quick-start/
theres even a web app you can set up to run your app
https://app.pm2.io/
but as of yet i haven't found a way to easily monitor the console.log output
so near as i can tell the best way to monitor the console long va the web app is with
console.log(`log`);
As this works flawlessly with my discord js bot, however my reddit bot doesnt seem to use it so it may be API specific on what can pass/use Console.log
Related
After android application expo building done and got APK/BUNDLE file ready to publish and access to google console and begin to fill all the forms stages one by one but when i got finish i face the open & closed & internal tests, for the first moment i didn't understand what these tests for.
After reading all the instructions i understad that somebody have to test my application, but who?
I saw that each one (open, closed, internal test) gives me a url.
i think this url is my application in google play but not for public just to give testers access to check my app.
Noteworthy the app got a temporary name.
I have give myself as a tester and app got installed by google play url ( talked above) on my phone, everything works fine but i dont know how to give pass to the tests.
thank you
After testing my app, every thing work very well, but still writen beside by app on the dashboard it is a draft and still writen not checked ?????
i get lost, what to do ?? maybe to wait for google testers ?? or maybe i forget something.??
please help....!!!!!!!
Open & closed & internal just for testing your app before it is available to all users. Testers can test your app if any bug happens while testing you have to upload a new app with resolved bugs. And if anything goes right you can directly upload it to production.
Draft in dashboard that means you have upload apk and doesn't rollout it to production.
I am attempting to make my own app with React Native, however it appears as though I'm working harder to get Expo to work more than I am trying to actually debug the app itself. I have tried with LAN, Tunnel, and Local but none of them seems to work. I will get it on some days and it will work fine.. for about 5 minutes and then it will time out or lose connection. Some days though it will just continue to try and load but will never actually pull up the app. I suspect this is because I am using my hotel wifi as well as a vpn (for security on a public network of course). I am wondering if there are any alternatives to expo that I might be able to use because this problem is starting to become very frustrating. Thanks!
You should be able to start Expo in offline mode so that your internet shouldn't be an issue. If you're using yarn the command would be yarn start --offline. You may also need to select Local once Expo launches.
Source: https://github.com/expo/expo-cli/issues/101
I'm taking an online course and created an app for a previous project and ran it on localhost:8000. I did use service workers if that matters. Now I'm working on a new app, also on localhost:8000 but it is still showing the previous app. If I go to the page in firefox, I see the app I'm working on but I need to see it in chrome. I never opened my previous app before in firefox, which is probably why I can see the new one.
Any idea what's happening here and how to fix it?
Thanks,
Michael
You should probably check your terminals if you have left your previous server running, and change the port to view your current project.
Basically, when I make mistake somewhere and the app crashes, no matter what I do, it stays crashed. Deleting last changes, restarting the server, nothing... So, I have to create a new project, copy everything to a new project, and it works.
Help please, I have no idea what's going on.
Running the latest version of Meteor on Linux Mint 18.2.
When you get the message "Your app is crashing" in the browser, I think it has given up, and you need to refresh the brower. In fact, refreshing the browser is sometimes necessary anyway.
Meteor detects changes to files pretty well, but sometimes struggles with new, deleted or moved files, and you may need to restart meteor and refresh the browser. You shouldn't need to copy to a new project.
I'm working with a Classic ASP web app that typically runs well considering the old technology. It is an online support chat application that basically refreshes the client side Live Monitor page every 10 seconds to see if there are any pending chat requests. The past few days, a lot of our users are having a problem where this page either just ends up refreshing and going blank white (with no html in view source), or it goes to a generic IE error page "This program cannot display the webpage" - the same error you see when you are offline. I was able to recreate the issue after hours when I was the only user in the chat system, so it's not a matter of an overloaded server I don't think.
I've tried the following to no avail:
Recycle Application Pool
Reboot IIS Server
Change refresh from javascript to meta tag
Check IIS Error logs (nothing)
Check IIS event logs (nothing)
One thing that seemed to work for me, but didn't work for everyone else, was to disable our network Proxy server settings in the browser. Once I disable this, I can't get it to error out anymore... however, other users aren't quite so lucky.
Any thoughts on where to go with this? I'm at a bit of a loss here...
Thanks,
Shawn
We are finding the same problems in a .Net solution. It looks as if the issues are related to SQL Locking so we're working on those as we find them.