If I want to connect via lan in different React Native projects, the same app always loads me, if I do it with Tunnel if the current app loads me,
I have seen that if I change WIFI, the LAN connection works and it loads the current app, but if I return the WIFI from my house, again the problem, it always loads the same app (old app)
Do you have any idea why this happens?
it sounds like Expo client is unable to connect to your computer over LAN and so it is falling back to the cached version from the last successful loading attempt
Related
I am doing a side project of transitioning my companies inhouse accounting app to a flask based web site.
I was just testing today to see if I could deploy onto the local network for everyone to access, and that worked will enough however it was my computers local ip ie something like 192.168.1.212:5000.
Is there a way I can run the flask app off my computer and on my computers local network where they could go to something like ourcompanyapp.com and get the app?
I am testing out the load tester from shiny and I am having trouble recording a session. From this youtube video from Rstudio https://resources.rstudio.com/webinars/load-testing-shiny-alan-dipert , the instructor mentions grabbing the url of the deployed application. I have tried both the url from my server/browser application and the url from my deployed application on shinyapps io. I have also tried running it on Rstudio Cloud and I am redirected to a login which then shoots me to a 404 error. I have tried getting the URL from Mozzila, Microsoft Edge, and Chrome without luck.
library(shinyloadtest)
#server application
record_session("http://127.0.0.1:3793/")
Error in curl::curl_fetch_memory(appUrl, handle = h) :
Failed to connect to 127.0.0.1 port 3793: Connection refused
#deployed shiny app
record_session(" https://finance.shinyapps.io/PrivateApp/")#this is not the real url
Error in .subset2(public_bind_env, "initialize")(...) :
Recording shinyapps.io apps is not supported
I am looking to find the right url to add to record_session so I can begin load testing my application. Thank you.
From the package's vigentte and on the GitHub thread the author was clear that you cannot benchmark against a Shiny app hosted on shinyapps.io:
Under Deployment Limitations it says:
1. WebSockets are required: On RStudio Connect and Shiny Server Pro, SockJS is used instead of plain WebSockets in order to support browsers and load balancers that don’t support WebSockets. Even though Shiny works in the absence of WebSocket support, shinyloadtest does not.
2. shinyapps.io unsupported: Applications deployed on http://www.shinyapps.io/ can’t be recorded or load tested.
Instead, the documentation suggested that you should install the package on your development machine.
Otherwise, shinyloadtest works perfectly fine (tested on multiple versions of R 3.5 and above). The function record_session() takes the URL of the deployed application as an argument:
shinyloadtest::record_session('https://your-deployed-shinyapp.com/')
Taken from the documentation:
Running the function will open a browser displaying the app. Once open, interact with the application as a normal user would and then close the browser. After closing the browser window or tab, a file will be created that contains a recording of the session. This recording, written to recording.log by default, will serve as the basis for the load test.
I am using django for a REST API at my company and have a few people using the first small part of my app via a Samsung tablet. They connect via WiFi to a angular front-end on Apache, that makes API requests to my django development server.
But every now and again the server just freezes intermittently. The front end would work and you can navigate it, but no API calls are going through. And then when ever I press CTRL+C on the development server console, suddenly all the request go through. Depending on how long someone have struggle, there may be 20 API requests that all go through.
At these moments even when I change something in Django in vs-code, nothing happens server side, but when I press CTRL+C suddenly even ALL the server restarts also go through. So I can see that all the request are standing in line just waiting for the server to wake up and then they are all processed. It also looks to me if this mostly happens with the tablet (and not my desktop), where we are using Chrome.
I read that the server is now multi threaded, so that can not be the problem, and I also do not have anti-virus that can stop the server requests.
I do not really know what else to say, it has been 2 weeks of frustration now and continual searching for answer with no luck.
I suspect that the issue is with you using the dev server, where one request is taking too long. If you already have apache installed you can use mod_wsgi to connect to Django like described here
Django With Apache
I have a website that I would like the customers to navigate to a page where it runs a program that I wrote. However, the program is on a separate server. How might I run the application from that remote server onto the server that hosts the website?
It looks like ideally I'll have my web host as GoDaddy.com and I'd like to run my application from that website.
Any thoughts?
What kind of technology are you employing to deploy the apps? ASP? PHP?
It seems that you were actually trying to "Window" the app on another server to your current site, if that's the case you can just simply link the app inside an iframe of your site.
Reference -http://www.w3schools.com/tags/tag_iframe.asp
I'm writing a django app that communicates with remote service (on my VPN but not hosted locally). I can successfully communicate with the service via the django shell but when I try to call the exact same function, posting the information from a webform, the development server dies.
I would have thought the shell and the development server would behave exactly the same way. The only thing I could think of was that the shell might be more 'patient', waiting for a response?
The communication happens via protocol buffers.
Help!
The developpement server is single-threaded so if you open another connection it hangs the server.
You could try for dev purposes : http://github.com/jaylett/django_concurrent_test_server
works very well for me
Or use a real configuration, apache+wsgi for example