I'm using webpack dev server to play with a little front end project and I am experiencing different default styling when accessing a project on localhost as opposed to accessing it via my local IP.
Does anyone have an explanation for why this might be?
Chrome Version: Version 61.0.3163.91 (Official Build) (64-bit)
Webpack dev server version: 2.6.1
Related
On my Windows machine, I noticed that when I hover my CSS class name in a .jsx file I'm able to see a hover menu to show me what the actual CSS is. However, I'm unable to recreate this on my Macbook Pro. I also don't have this capability for .html files.
On my Windows, I have the HTML CSS Support extension, but I also have it on my Mac. I tried looking at other suggestions that said to use CSS Peek as well, but I installed it and it didn't do anything.
Here is my Windows VS Code version:
Version: 1.63.2 (system setup)
OS: Windows_NT x64 10.0.19044
Here is my Mac VS Code version:
Version: 1.65.2
OS: Darwin x64 18.7.0
Is there an extension I need to install or is there a setting I need to use?
I had Tailwind CSS IntelliSense installed on my Windows machine without realizing it and that did the trick.
I'm using a Windows 10 machine to connect to a remote Ubuntu 18.04.4 LTS machine via Windows' built-in Remote Desktop Connection (RDP) using xrdp 0.9.5.
The setup was working fine up until now.
However, I'm getting a weird error when trying to use bokeh through the Windows' remote desktop connection:
bokeh: command not found
Obviously, bokeh 1.4.0* is installed, but none of the bokeh commands work. I always get the same error message from above. I also can't pip install bokeh as it says bokeh is already installed. On the remote Ubuntu machine, the bokeh commands get recognized fine when running them directly on the Ubuntu machine (no remote connection).
Did anyone face similar problems or knows a possible solution?
*I can't really upgrade to the newest bokeh version because I unfortunately need to stick with Python 2.7 ...
Trying to upgrade Nexus 2.1.4 Repo to 3.X. This is what i have done till now and what what went wrong!
-- installed the 3.0.2 version on the same machine in a different port (8090) Then opened the UI and tried doing the upgrade agent and there was no upgrade agent in 3.0.2.
-- so i installed 3.1 on the different port and came across a java exception error in nexus Repo UI while migrating stuff from 2.1.4 (installed on port 80). I found out that one need to be at-least on 3.2.4 V to migrate.
-- now i installed 3.6 on a different port (8082)in the same machine. couldn't start nexus service now. which i was able to for other nexus version in other ports.
I am trying to push a Windows docker Image to a Nexus Repository Manager version 3.3.1 running on Ubuntu Linux. I am getting blob unknown: blob unknown to registry. BTW, pushing Linux Docker images works fine.
Can you use Nexus Repository manager running on Linux to store both Linux And Windows Docker images? If so, how is that done?
P.S. I am pushing from a Windows 10 Computer.
Thanks in advance
This is a known request: https://issues.sonatype.org/browse/NEXUS-11865
You can read up a bit about it at that link. No ETA for support as of yet.
I use Windows 8 and installed Virtualbox so i can access to a Linux (Ubuntu) System.
The most i still did to do this - so at this moment i have a working Virtualbox with Ubuntu 14.04 LTS.
In my case i need this Virtualbox with Linux for meteor.
The problem:
meteor uses nodejs and so i need to have symlinks access (i think its symlinks - i read a few about it)
Reference: How to run meteor app inside an Ubuntu VrtualBox and edit using an editor on a Windows host?
He describes the same problem i have now:
Error: EROFS, read-only file system '/media/sf_Shared/Dropbox/dev_uhurajr/chat/.meteor/local/.build320446.build/programs/server/npm/logging/main/node_modules'
So i tried to enabled Symlinks on my host (windows) this way:
VBoxManage setextradata YOURVMNAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/YOURSHAREFOLDERNAME 1
Reference: http://www.ahtik.com/blog/fixing-your-virtualbox-shared-folder-symlink-error/
This works fine! When i check the extradata for my VM the field SharedFoldersEnableSymlinksCreate is on 1
I set this value for 2 folders. The shared folder on Windows and also the name of the shared folder on my Linux VM.
But .. the same problem. The following error occurs everytime meteor tries to write symlinks:
Error: UNKNOWN, unknown error '/media/Projekte/test/.meteor/local/.build320446.build/programs/server/npm/logging/main/node_modules'
So whats the right way to get this working ?
Guessing you were using Virtualbox version after 4.0, please:
Enable symlinks VBoxManage.exe setextradata YOUR_VM VBoxInternal2/SharedFoldersEnableSymlinksCreate/YOUR_SHARED_FOLDER 1
Run VirtualBox 'as admininstrator' on Windows.
Replace the YOUR_VM and YOUR_SHARED_FOLDER with your own value. You can check the value via VBoxManage.exe getextradata YOUR_VM enumerate
VirtualBox enabled symbolic for shared folder since 4.0, it's Windows permissions blocking you. You can either enable the permission for user or simply run VirtualBox as an administrator.
Please to refer the Virtualbox documentation:
Doc updated, please refer to the doc Shared Folders:
Starting with version 4.0, VirtualBox shared folders also support symbolic links (symlinks), under the following conditions:
The host operating system must support symlinks (i.e. a Mac, Linux or Solaris host is required).
Currently only Linux and Solaris Guest Additions support symlinks.
I made a development vm with setup and run scripts.
https://github.com/gfk-ba/meteor-dev-vm
Just put your meteor app in the app directory and follow the instructions in the readme.md