| docker-compose up -d | |
| docker attach myapp_web_1 |
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
| /* Delete the tables if they already exist */ | |
| drop table if exists Movie; | |
| drop table if exists Reviewer; | |
| drop table if exists Rating; | |
| /* Create the schema for our tables */ | |
| create table Movie(mID int, title text, year int, director text); | |
| create table Reviewer(rID int, name text); | |
| create table Rating(rID int, mID int, stars int, ratingDate date); |
| def valid? version | |
| pattern = /^\d+\.\d+\.\d+(\-(dev|beta|rc\d+))?$/ | |
| raise "Tried to set invalid version: #{version}".red unless version =~ pattern | |
| end | |
| def correct_version version | |
| ver, flag = version.split '-' | |
| v = ver.split '.' | |
| (0..2).each do |n| | |
| v[n] = v[n].to_i |
There are two modes when you don't want Certbot to edit your configuration:
Webroot is better because it doesn't need to replace Nginx (to bind to port 80) to renew certificates.
In the following, we're setting up mydomain.com to be served from /var/www/mydomain, and challenges will be served from /var/www/letsencrypt.
The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.
When you want to generate the flame graph, run the following (folder locations taken from install script):
sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0
| diff --git a/random.c b/random.c | |
| index e669e98..9334921 100644 | |
| --- a/random.c | |
| +++ b/random.c | |
| @@ -521,7 +521,7 @@ fill_random_bytes_syscall(void *seed, size_t size, int unused) | |
| CryptGenRandom(prov, size, seed); | |
| return 0; | |
| } | |
| -#elif defined __linux__ && defined SYS_getrandom | |
| +#elif defined __linux__ && defined __NR_getrandom |
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm