Hi I'm trying to make my first meteor app. I just made an app and have run it. I've also upgraded to latest meteorite and meteor. I just created a new app and have run it.
App running at: http://localhost:3000/
But I cannot view this webpage on my host computer. I'm running meteor on an ubuntu vm.
It was working before I updated meteorite and meteor and installed the iron-router package to an app I'm working on.
check in the console you might have the error as template is not defined, Meteor is not defined etc...
I too was unable to connect to the Meteor App that was being developed on a centos VM.
The followuing worked:
Setup:
Windows 7/8.1 with Following tools installed:
Putty
VMW Workstation
Centos VM (Server or GUI based)
Chrome/Mozilla Browsers
Launch the VM from VMW Workstation
Console into the VM using Putty
Launch the Meteor App. Will show its listening at localhost?3000
Launch a new session of Putty.
Go To SSH-Tunnels - Source: 3000, Destination - Localhost:3000. Save this settings
Connect to the VM with these settings
Launch the browser and and navigate to localhost:3000
Worked for me, hope does for all
As you have determined, the message on the vm regarding localhost:3000 refers to the vm that is running meteor, and localhost on your computer refers to your computer.
The secure fix for this is to create an encrypted tunnel to connect localhost:3000 on your computer to localhost:3000 on the remote computer.
Start the meteor app on the VM so that you get the message about it being ready on localhost:3000
On the local computer open another terminal window and initiate a second connection to the VM with:
ssh -L 3000:localhost:3000 yourUSER#remoteHOST
This assumes you are running Linux. If you are on Windows, look at the options for your SSH client. It may have similar options to create tunnels.
Open a web browser on your local computer and go to http://localhost:3000
The ssh tunnelling software will sense the connection to localhost:3000 on your computer and will connect you to localhost:3000 on the remote, forwarding the data through an encrypted tunnel.
If this seems like a lot of trouble, there are paid developer platforms like http://nitrous.io that can run meteor and have a web based IDE that can simplify this sort of thing for you so you do not need to run the tunnel. Another way to simplify is to not use a remote VM, but install Meteor on the home computer and only copy the code to a VM when it is finished and ready for production.
If you don't want to run on localhost:3000 at all, but on the webserver on port 80, you might check to see if there is an environment variable that switches the code from development mode to production.
Related
The way opencpu "productionnise" an app is to get your own linux server then to install your package and then launch your app.
Before that, I am still in a dev environment, where I work on a windows machine.
I would like to run the app locally behind a firewall and send the ipv4 link of my machine to a collegue, to allow him to test my app, using my machine as a server.
Is there a way to serve my app on the Ipv4 address of my windows machine?
From what I understand, on a windows machine, the adviced architecture would be more to use a vm to emulate a linux server. But if there is a way to avoid it, it would be nice.
You can start a local OpenCPU server via opencpu::ocpu_start_server(), which uses port 5656 by default. If you then point your browser to http://<your-ip>:5656/ocpu, you will be greeted with the normal OpenCPU interface.
Good morning,
Working on installing Meteor on windows using the following guide:https://gist.github.com/gabrielhpugliese/5855677
As pointed out on other posts its a little dated and I needed to install meteor separately, which I used this guide: Unable to install meteorite on Ubuntu VM
Currently, my set up can do the following:
files stay in sync between vagrant and windows
localhost:3000/ is working on the server
What I still need help completing:
when opening localhost:3000/ in my windows browser, I get the "This webpage is not available
I know that the vagrant VM is correctly serving the app because I opened a new instance of vagrant and curled the localhoust:3000/
I am actively working in django and node and can successfully run apps locally on :8000 and :8080, I tested the meteor app on those ports but still couldn't connect. I also created a windows firewall port exception on 3000 but the results didn't change.
I know that there is a windows-preview currently out, but that is not working for me and I have an issue being tracked in gitHub.
Thank you in advance.
One thing that might be worth mentioning is it is somewhat possible to use Meteor on windows.
More details here: https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows.
With your vagrant machine it sounds like there is a problem with port forwarding on your localhost machine to the VM's ports.
One possible simple way to get passed this is to get your Ubuntu machines IP address and simply load it up using http://<ip address>:3000.
I'm not sure why the port forwarding isn't working on your machine. In general the reason is provided when you run vagrant up, if there was an issue.
I've used PuPHPet to set up a development environment and did "vagrant ssh" to get into the machine. After that I installed meteor via curl https://install.meteor.com/ | sh, which worked as expexcted. I thought it would install it to the sync folder I have set up but it doesn't seem to be there. Can I find the file structure of the virtualized machine on my Windows PC?
How does it work? If meteor tells me I can access my meteor app via localhost:3000 how do I access this on my Windows PC?
I'm not so familiar with vagrant and windows, but give this a try.
Login with vagrant ssh
Open terminal and type hostname --ip-address
Paste <yourip> localhost in your hosts file on your windows machine system32\drivers\etc\hosts
Now, all your localhost requests in your browser are send to your vagrant box. I'm not sure if Meteors standard port works with vagrant, so try something like meteor -p 2000 or meteor -p 8080
If you want something like myapp.dev in your browser, you have to use virtual hosts. I'm only familiar with apaches virtual host system, but meteor is using nodejs so i don't know, what would be the best practice here. :/
I am transitioning my debian setup into one where all debian-repository external apps run in dedicated docker containers.
In this context rstudio, of which I am a heavy user, has me puzzled ... does anybody have insight into whether it's possible to run it as a client to remote R installation?
What is a very cool feature of RStudio is RStudio Server. You install RStudio Server on you Ubuntu server and log in to a specific port where RStudio Server is running. You then get your full RStudio interface in your web browser. This allows you to run all your R analyses from any computer that has a modern browser and an internet connection.
R then runs on the remote server, asking almost no resource from the computer you are connecting from.
I am working on a small website based on an example ServiceStack project. It is a standalone web app so that there is no need for IIS etc. Currently I start the server at http://localhost:8080 and opening the website in my local browsers seems to work fine.
My PC has a dedicated IP and I hope to test my server from another computer. I can successfully get a Python server running using python -m SimpleHTTPServer 8000, so network is working fine.
But the remote computer cannot access my ServiceStack server. I think there should be a simple setting somewhere to get it working. But I searched online, there is much information about IIS and ASP.Net. But my app is standalone and is independent of Asp.net. It is supposed to be running on Linux as well as on Windows. (Though I will only deploy on a Windows machine now.)
It will work fine on your local computer because the firewall doesn't block local traffic. If you want any other computer to access services running on your machine you will need to open the ports on the firewall.
This can be configured from the Windows Firewall in Control Panel