I have been playing around on Windows 7 and tried to run my Meteor app locally with a 500 mb file in the private folder. It doesn't even boot up. Here's the sequence:
meteor create test
cd test and meteor
default app loads fine on localhost:3000
create a /private folder and place a 500 mb text file there
meteor dies partway without ever loading on localhost:3000
Removed /private folder and re-ran.
Works again.
Anyone knows what may be causing this problem?
Related
I downloaded and installed odoo and it was running fine on my server, then I added a custom module it was uploaded successfully but it wasn't reading the model files and other view files I created, so I restarted the server and then I was receiving the following error. My database is connected and there is no such issue I even tried to start it manually but it did not work, so what's the solution to this problem?
Error details
I have a .NET Core 3.1 app (api) that i'm publishing online and I'm using the publish method FTP in Visual Studio.
It works perfectly but when I try to publish again after coding, I always get these errors:
Publishing folder /...
Unable to add 'AutoMapper.dll' to the Web site. The process cannot access the file because it is being used by another process (550).
Unable to add 'projectname.API.dll' to the Web site. The process cannot access the file because it is being used by another process (550).
Unable to add 'projectname.Domain.dll' to the Web site. The process cannot access the file because it is being used by another process (550).
...
This goes on for quite some time on all the dll's in my project. The only way I can publish after working, is full resetting my PC, remove all bin and obj folders in my projects that have to get published, open VS and publish before doing anything else.
I suspect this has to do with VS still using the dll's somewhere/somehow while i'm trying to publish.
I have tried locating processes in task manager but haven't seen anything unusual/problematic that could cause this.
Any help regarding this would be greatly appreciated, because I like to update my API for every route I write to test on the deployed version aswell, but it's quite the hassle this way...
Thanks!
I don't think it's your pc. Error 550 is an FTP error. What I think is happening here is that when you publish your website via FTP and open your website in your browser what you actually do is run your application on your server.
When your application is running you can not modify the DLLs that are in use.
So why restarting your pc will fix the problem? It is because these hosting providers have a configuration that if no one requests a website for a while then kill the application. it is because of saving memory and cpu.
So when you restart your pc and delete bin and obj folders and rebuild your project that takes time and because in the meantime there is no request sent to your website your application is killed and now you can update your website with FTP again.
To test this scenario simply close your browsers and do not open your website for a while like half an hour and then try to update your website via FTP.
Or you can restart your PC and delete bin and obj folders but before pushing your files with FTP open your site in a browser. This must run your application and cause the 550 error again.
i have successfully upload my Asp.net core 1.01 website to Ubuntu 14.04 Vultr VPS with Nginix.
The problem is that whenever i change in my code on local development machine and upload published folder dll to server, its required to restart the application or server to view updated contents.
is someone help me to that without application or server restart. so i can just upload updated dlls via FTP and its show updated contents.
thanks
Use dotnet-watch
dotnet watch is a tool that runs a dotnet command when source files change. For example, a file change can trigger compilation, tests, or deployment.
It appears mup setup can't run without a mup.json file. But, it appears the mup.json file is primarily used for mup deploy. Reason I ask is I'm trying to execute mup setup on the host server and it fails without the server credentials but considering that I'm already logged onto the server executing the setup I don't understand why the mup.json is being required in the first place? I'm not deploying an application so none of the application-specific settings would apply, right? If I don't have a mup.json on the server then mup setup throws an error that the mup.json file does not exist. It didn't seem really clear on the meteor up web site. Thanks!
You should run Meteor Up from your local machine as that's what it's designed for. I wrote about how to deploy with meteor up a while back and that should help you.
In a nutshell I believe you're thinking about this the wrong way. With mup, meteor deploy and soon galaxy deploy, you no longer need to "upload" your files and then go and manage them from the server. Instead your files stay local, you deploy (which will upload them) and deployment sets up your server and file structure.
Misunderstanding on my part. mup setup is something you run on your remote machine, not the host machine.
I created a Flex app in a Windows XP environment using Flex Builder 3.
From the menubar, I selected "Project->Export Build Release" and moved the files from /bin-release onto my local server (WAMP).
I have a PHP file that connects to a db and delivers some data via XML
Everything works right on my computer. Then I tried to move the app to a mac.
I installed MAMP with the default settings (localhost:8888)
I can connect to the PHP file and get the XML by hitting the appropriate URL on # http://localhost:8888/...
Likewise, I can connect to the html template and the swf executes, but it doesn't seem to be getting the data back, and I don't get any debug info popping up.
Any ideas? Are there security settings enabled by default in Mac OS that would not allow a flex app to request data from a remote resource (i.e. http://localhost:8888/ in this case)?
what is the error that you get?
1. try to catch the FaultEvent
2. do you install any of flash debugger?
The trouble was with the MAMP installation. I reinstalled it, and the app worked.