I have a meteor app on my laptop (where I do development work on the app), and I would like to be able to work with it and/or give demos of it in situations where I do not have an internet connection.
How can I prevent meteor from automatically trying to download updates to packages when I run it, so that I can run my app without issues in an "offline" situation?
Note that this is different from the client (browser) being "offline" in the sense that it can't connect to the server. In this situation, the client and server are on the same machine and the client does have access to the server. But the machine is disconnected from the internet, so that attempts to automatically download package updates will incur at least a delay, if not errors, and I'd like to prevent that.
Use METEOR_OFFLINE_CATALOG environment var for that. But I would suggest not to set it up permanently, but rather to use it once.
So if you run meteor like this: METEOR_OFFLINE_CATALOG=1 meteor it shouldn't update any packages or meteor releases.
Related
I'm having trouble with setting up ACORE API's and then having them work on a website.
Background:
Azerothcore running 3.3.5 on a debian standalone server, this has the Database, Core files and runs both the world and auth server basically a standard setup that is shown in the how-to wiki.
I also have a standalone web server, on the same subnet, but it's a separate server running linux and normal web server stuff, this has a wordpress installation with azerothcore plugin for user signup etc.
I'm trying to add the player map (https://github.com/azerothcore/playermap) and the ACORE-API set of functions (server status, arenastats, BG que and wow statistics) (https://github.com/azerothcore/acore-api)
Problem:
I understand the acore-api must be run in a container (docker or whatever) on the server, which I have done and it binds to port 3000, I can then go to the local ip:3000 and it brings up this error. (all db's etc are connecting and soap is working)
error 404 when navigating to IP:3000
I do get a few errors when running NPM install seen here: I'm not sure if they would be causing any issues or not.
screenshot of NPM errors on install
But further that, when I put say 'serverstatus' on the webserver (separate server) and configure the config.ts file I can't seem to get anything to display.
I'm not sure what I'm doing wrong but is the same scenario for all of the different functions for the acore-api
How are these meant to be installed and function? I feel I'm missing a vital step.
Likewise, with PLAYERMAP I have edited the comm_conf.php and set the realmd_id, but when loading the page, I do get the map, but the uptime is missing and no players are shown?
Could someone assist if possible?
Seems like an issue with NodeJS version. Update your NodeJS to latest LTS version 16.13.0 (https://nodejs.org)
I've been using meteorjs for quite a while now on linux. But when I installed using the relatively new windows installer, I saw that the most basic example doesn't work on properly on my computer - win7.
The example is at: https://www.meteor.com/try/4
which runs perfectly on my ububtu, but on my windows - I see that no information is inserted into the db and all changes I make (add new "tasks") are only local to that page, and other tabs I opened were also local, and there was no "reactivity" (no information was shared between different pages).
I tried to troubleshoot it in some ways:
I made sure that MONGO_URL is not set, and then I set MONGO_URL to another db, and saw that even though that db reported "connection accepted", the oplog nor the collection updated (tasks) have any new information.
Tried different kinds of browsers (chrome, firefox). Both are latest in version.
See no errors in chrome console.
I am assuming that all writes are made to minimongo, which doesn't pass them on.
Is this somehow a known issue?
Any suggestions?
A few things you can try:
uninstall meteor & any separate instance of mongo (including cmd aliases). download a fresh copy & install. Create a new project in a new folder. If the DB had some weird bugged lock on it, this is sure to fix it.
download robomongo (or use meteor mongo) to insert a new doc & see if it sticks. If it does, you know mongo isn't the problem.
Check that autopublish and insecure are installed. If they are, when you complete step 2 you should see a new doc in the app. If you do, then the DB can communicate to the app, so the problem has to be with the client-side saving to DB. Try a meteor method instead of a direct insert. If you don't see a new doc, then the data from the DB can't reach your client, which means your firewall (yes, it can screw up localhost requests, too) is to blame. Turn it off, make sure ports 3000 & 3001 (mongo) are allowed full access & that it doesn't do anything wonky with websockets.
I would try re-installing Visual Studio 2012 and Python 2.6/2.7, then re-installing Node and then Meteor.
Recently I added email sending capability to my Meteor app, using both the email package, and the account registration APIs to send emails. The other day, after having tested this thoroughly on my dev machine, I deployed it to our production server using Meteor Up. Once deployed, I did a quick check that the email APIs were working properly, and let it be. A day or two later, I made some minor changes, wrapping these email APIs in a Meteor.defer method to speed up the UI. I tested the changes locally (all fine), and re-deployed. I also ran apt-get update on my server after seeing a notification there were some new security updates available. After doing this, the email system no longer works. I tried reverting back to my previous configuration, and it still isn't working. I'm getting a timeout error:
Exception while invoking method 'forgotPassword' Error: connect ETIMEDOUT
I was wondering if anyone had any ideas on what might be causing this timeout (a blocked port?...how can I diagnose this?). Given my SMTP port is working on my development machine, it doesn't seem to be an issue with my code, but rather either with the MUP deployment, or Ubuntu configuration. I'm not super familiar with configuring Ubuntu servers. Any suggestions on how to go about de-bugging would be greatly appreciated!
We got a similar problem, and it was solved by opening the needed port in EC2. thanks to https://kylegoslin.wordpress.com/2012/06/05/116/
I am developing a meteor application. I noticed that the meteor server sometimes suddently crashes, this makes me think that it might not be optimized for production.
In a production environment, should I consider to add/remove some packages? Which one? And what are the best settings? I just want to make sure to have a reliable server that stay up all the time.
Have you taken a look at meteor up yet? It will set up a production quality server for you. I've used it for several production applications and it works great.
As far as adding/removing packages goes, I've never ran into any problems with installed packages running on production. A couple of my apps have about a dozen or so packages installed. But if you suspect that a package might be causing the problem, I would go to atmosphere and search for your packages and make sure that they haven't been flagged. You'll see a bright red flag next to the package name if it's been flagged by the community as "not working".
Maybe also check for issues on GitHub.
If you do decide to use meteor up, after your app has been uploaded to the server, you can check the log s for any problems.
mup logs -f
Tools like MongoLab remote connection and RockMongo require a permanent URL, so the URLs generated by "meteor mongo --url" that are only valid for 1 minute don't work for long.
If you're on a mac I would recommend that fononauts build of MongoHub you put up, the ordinary Mongohub is quite buggy & on Windows use MongoVue which is perhaps the best one i've used of all.