In Git you can add a submodule to a repository. This is basically a repository embedded in your main repository. This can be very useful. A couple of usecases of submodules:
- Separate big codebases into multiple repositories.
a.album-hover:hover span.overlay { | |
-ms-filter: "progid: DXImageTransform.Microsoft.Alpha(Opacity=80)"; | |
filter: alpha(opacity=80); | |
opacity: 0.8; | |
} |
<koken:if false="pjax"> | |
<koken:include file="inc/head.html" /> | |
</koken:not> | |
<koken:load infinite="true"> | |
<koken:head> | |
<meta property="og:site_name" content="{{ site.title }}" /> | |
<meta property="og:title" content="{{ album.title strip_html="true" }}" /> | |
<meta property="og:description" content="{{ album.summary strip_html="true" }}" /> |
import java.io.File; | |
import lombok.extern.slf4j.Slf4j; | |
import org.springframework.beans.factory.annotation.Qualifier; | |
import org.springframework.beans.factory.config.PropertyPlaceholderConfigurer; | |
import org.springframework.context.annotation.Bean; | |
import org.springframework.context.annotation.Configuration; | |
import org.springframework.context.annotation.Profile; | |
import org.springframework.core.io.ClassPathResource; |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com
, example2.com
, and example1.com/images
on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
the best way (I've found) to completely uninstall node + npm is to do the following: | |
go to /usr/local/lib and delete any node and node_modules | |
go to /usr/local/include and delete any node and node_modules directory | |
if you installed with brew install node, then run brew uninstall node in your terminal | |
check your Home directory for any local or lib or include folders, and delete any node or node_modules from there | |
go to /usr/local/bin and delete any node executable | |
You may need to do the additional instructions as well: | |
sudo rm /usr/local/bin/npm |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)