I've got sort of a simple problem, but I can't seem to find any conclusive answers on the web. So, I have Ubuntu Server running in VirtualBox with Ruby and Rails installed.
What I want to do, is edit the files in the VM over SSH using RubyMine 5.0 on the Windows host machine (just like I can in Eclipse).
The problem is I can't find how to do that. I'm pretty sure it can be done, because I've found some related articles on the web, but none of them show me how I can configure RubyMine to do that.
I've searched every option in the menu and I can't figure it out by myself, so a "to the point" explanation would really be of help.
Thanks
There is no way to do this natively in RubyMine. My solution is to mount the remote filesystem to a local folder using sshfs.
Linux you can get sshfs through your package manager.
OSX you can get it here make sure to install both OSX fuse and SSHFS. The version on HomeBrew did not work for me on OSX 10.9.4 so I recommend using the packages from the link.
Windows you can use win-sshfs, I've had good results using Chocolaty to install win-sshfs
To use on Linux/OSX:
Open your terminal.
mkdir MountFolder
sshfs user#server.com:/path/to/project MountFolder/
To use on Windows:
Use the GUI.
After you've mounted the remote file system open RubyMine and select Open Directory and browse to the project.
This is the best solution I can come up with until JetBrains supports it natively.
Related
I'm trying to test my development environment and keep getting this error while going through the "Building Your First Network". I've installed the prerequisites on a Windows 10 Home edition so I'm using Docker Toolbox. The error is described as follows and happens just after a execute the ./byfn.sh up -l node command:
2019-11-14 17:06:26.982 UTC [msp] loadCertificateAt -> INFO 002 Failed loading ClientOU certificate at [/var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem]: [could not read file /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: open /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: no such file or directory]
As you can see there is a backslash just before the ca.example.com-cer.pem which I think is causing the problem. Anyone have an idea of how I might solve this issue?
Docker Toolbox for windows doesn't provide a great experience for users. It's limited in how it can share windows directories with linux containers running in the linux VM it creates. I believe it can be made to work but you have to use very specific folders in your home directory and you would have to google it to find all the details but it's a lot more of a hassle.
You have other options of course
Upgrade to Windows Pro and use Docker for Windows (which doesn't have the same sharing limitations, but still not a great experience and you can still encounter problems sharing the directories)
Install a hypervisor such as virtualbox and run a linux desktop distribution such as ubuntu or mint and use that instead (which I would recommend and would suggest ubuntu 18.04 mate edition)
Wait until next year when hopefully microsoft will release WSL2 for everyone (including home edition) and then Docker won't need a linux VM running and it should be a much better experience trying to run linux containers on windows.
As mentioned by lindluni here
Backslash problem in Hyperledger 2.0.1 when orderer/peer look for .pem files
the problem arises when one creates crypto artifacts under Windows since "golang filepath.Join uses the current OS's filepath scheme". Hence, under Windows backslash is used in all the generated config.yaml files found in crypto-config/*. One can replace this backslashes before the deployment to fix the issue.
I have two CentOS VMs which use Jenkins to run automated tests through firefox. Both have firefox installed. Both versions of firefox are the same (firefox-56.0.1). I do not know if they are both x86_64 or some other type, but whichever they are, they are the same. (I am using the same .tar.bz2 file. I copied it from one instance to the other.)
In one instance, I am able to run firefox. "firefox --headless" returns "*** You are running in headless mode."
After copying the .tar.bz2 file to the other instance and installing firefox, I find that the new instance does not have the same performance. "firefox --headless" returns the following:
XPCOMGlueLoad error for file /usr/local/firefox/libmozgtk.so:
libgtk-3.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
What might explain this difference? It appears that I did something right in the first instance, but I cannot tell what. Is there some setting that will prevent firefox from trying to use the "libgtk-3.so.0" file? This file does not exist on either instance.
I've seen this question elsewhere, but the answer seems to focus on versions (I know my version has worked in the first instance) and a particular bug that has been backlogged (this bug only bothers me for the new instance).
Problem solved minutes after asking the question.
Simply run:
yum info gtk3
Check if gtk3 is installed. If not:
yum install gtk3
My old instance had gtk3 version 3.22.10 installed. My new instance had the same available but not installed. I don't recall seeing this in any of the guides to running firefox headlessly, but a search result that I did not originally think worth checking was able to resolve this rather quickly. Credit to the folks at https://forums.fedoraforum.org/showthread.php?310652-Udating-Firefox-fedora-19
For Ubuntu or Debian distros use:
apt-get install packagekit-gtk3-module
You probably installed the wrong firefox version for 32bit on a 64bit system.
try downloading firefox with this portable installer download-mozilla-portable.sh which should work on a 64bit linux (tested in Ubuntu 19.10)
I'm trying to configure an OS X box with Samba using SMBUp. I installed SMBUp, installed SAMBA through it, and configured my users and shares. The only issue is when I check which protocol version I'm using, I'm using SMB1
Ok, fine. But when I try and change the protocol version in SMBUp, there is only LANMAN/CORE/NT protocols as options. I tried manually editing the configuration file in /opt/local/etc/samba3/smb.conf and changing the minimum protocol to SMB3, but that didn't work at all.
When I used OS X's built-in file sharing, I could connect via SMB3, but I only got around 10MB/s over ethernet... Not very good at all.
I'm very new to this whole thing and I couldn't find much documentation pertaining to my issue.
Any suggestions?
Thanks
EDIT:
I tried using (rebooting after running it):
sudo sh -c "echo '[default]' >> /etc/nsmb.conf; echo 'smb_neg=smb3_only' >> /etc/nsmb.conf"
But that just prevented my share from mounting.
The version of Samba included in SMBUp is lower 3.6.something. SMB2 and SMB3 support was added in 4.0. Now I just have to figure out how to update Samba...
Cheers
EDIT:
Right, Samba devs stopped supporting OS X and I keep getting an error about not having GnuTls installed even though it is installed. So I can't compile it.
Great. I'm going to go die in a hole now.
i want to use internet explorer on my mac, is there any way to install.
i need it as there are some websites which can open only in internet explorer, its a loss for me that i cant open websites on this safari
kindly help me if any one knows or using IE.
do you have any idea about virtualbox. is this help to download IE for mac
http://news.softpedia.com/news/How-to-Run-Internet-Explorer-on-Mac-OS-X-391323.shtml
above link shows how todownload virtualbox and to install it
thanks
I find that the ievms project that is referred to in the softpedia link you provided is pretty quick and painless to setup on OSX. Once you have installed VirtualBox it will download and install the image for you automatically.
Note that it seems like you only need one IE version (and not all of them) so make sure you specify a version to download in the curl command, for example to install Internet Explorer 8:
curl -s https://raw.github.com/xdissent/ievms/master/ievms.sh | env IEVMS_VERSIONS="8" bash
Just run this command in your Terminal and it will do the rest.
Note: I've put version 8 as an example because it would be quicker to download than newer versions and is probably enough for your usage
All,
Am trying to get Node.js to work on Vista machine.
I installed Cygwin (as per the Github instructions) which appears to have been installed correctly. However, none of the commands are executing.
Are there any tutorials for the stages after the Cygwin installation?
PROBLEM: When any command is executed, I get 'Bash: command not found' error.
Not even command like 'c:\cygwin\bin' is executing.
When I type 'user' in cygwin command prompt, I get 'ntvdm has encountered an system error. Parameter incorrect'.
I thought the above error may be due to the firewall, disabling the firewall did not have any effect, running the program with admin rights also did not change the results...
Am confused and would love to get some guidance on what steps to go with next on getting Node.js up and running on a Windows Vista machine.
Many thanks,
UPDATE1:
We managed to make a bit more progress. It appears that we had not installed all the relevant files related to Cygwin. Upon re-download and reinstalled, it ran well, however, we have driven into another error. Error we get:
How to compile/install node.js(could not configure a cxx compiler!) (Ubuntu).
We followed the instructions as per the above thread (3rd post from top for Windows machines), however, we are still stuck at the same error.
Any guidance please?
Have you tried just using the Windows self contained binaries? http://node-js.prcn.co.cc/ This way you actually don't need to bother with Cygwin.
At first, i tried it your way too, using Cygwin. After smashing my head for the 10th time against a wall i just stopped trying and found a much cleaner solution.
I'm using VirtualBox running a Debain guest system to locally develop on my Windows 7 machine. Using VirtualBox, you can easily set up shared folders or port forwarding for node apps between your Windows machine and your Debian guest system.
Since you are using a plain Linux-system, all the compiling-pain is blown away.
If you plan to run node.js in production on a windows system: don't. I hardly believe node.js will be ever stable enough on windows-based systems using MINGW/Cygwin...
People seem to run into problems with Cygwin because they think that they are using a Windows machine.
If you install Cygwin, and open a bash shell prompt using the Cygwin icon, you are now in a UNIX environment and everything works the same as it would on UNIX. That includes building node.js.
I think you added some info to the question and I can see your problem. Yes, normally on Cygwin it has been possible to build node.js just as you would on any UNIX system, but that is no longer possible on Windows 7. Before running ./configure you have to:
Close all cygwin apps.
Double-click on C:\Cygwin\bin\ash.exe
Run ./rebaseall and when it completes, run ./perlrebase.
exit from the ash shell window.
At this point Cygwin will be back to normal and you can ./configure and make install.