I am working on windows and have installed openstack on virtual box (ubuntu vm). I want to enable debugging for this code hence enabled remote debugging using ssh on VS code. Now i want whenever i run a cli command on cinder openstack (terminal) i should be able to see the flow of code. Please help.
I tried remote debugger with different python files to start in debugging mode but unable to get it.
Related
I noticed that on Ubuntu 20.04, a lot of software is made available through snap and it does not even appear in the distribution's "sources".
This is all good, but when you try to run an application that has graphic output and have it connect via remote X11 to your machine, snap seems to be Unable to open X display. Which is strange, because gnumeric (for example) runs as a remote X11 application just fine.
I suspect that this is a configuration problem. Any ideas on how to run a remote X11 application via snap appropriately?
Try running this on the remote host before launching the snap application:
export XAUTHORITY=$HOME/.Xauthority
I have an ASP.NET/IIS site setup using vagrant. Is there a way to remote debug from VSCode on my local machine? Having a difficult time find info on this
I see remote debugging but it sounds like it's only for visual studio
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer?view=vs-2017
According to the documentation remote debugging is not part of VS Code:
VS Code does not support 'remote debugging' by itself. Remote debugging is a feature of the debug extension you are using and you should consult the extension's page in the Marketplace for support and details.
I'm trying to debug some code running on a server using the Visual Studio 2015 Remote Debugger. I can get connected and view all the running processes but when I try to connect to the w3wp.exe process it is having none of it.
From my fiddling I've noticed that it will connect to apps that are running in the Managed (v4.0.30319), x86 mode, however if it's just x86 it doesn't connect and I'm guessing this is because it's been compiled and isn't in MSIL.
I've copied over the files from my machine, by passing all the precompilation that we were doing, as much config set to debug as I can find and even still when I try to attach it still reports x86 with no mention of any managed code.
Just to clarify, this is what I see when attaching on my local machine:
And this is the same app running on the remote server:
Does anyone know how to force the server to run in managed mode, or is there another reason I can't connect to the remove debugger?
Thanks
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.
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.