First identify your image.
$ docker ps --format "{{.ID}}: {{.Image}} {{.Names}}"
3d2fb2ab2ca5: jenkins-docker jenkins-docker_1
Then login into the image as root.
$ docker container exec -u 0 -it jenkins-docker_1 /bin/bash
First identify your image.
$ docker ps --format "{{.ID}}: {{.Image}} {{.Names}}"
3d2fb2ab2ca5: jenkins-docker jenkins-docker_1
Then login into the image as root.
$ docker container exec -u 0 -it jenkins-docker_1 /bin/bash
Starting a personal node project could be easy; starting a team node project could be challenging.
I am a developer currently working in SEEK Australia.
In my experience, common mistakes developer make when starting a projects are:
# Location: /mnt/c/windows/system32/drivers/etc/hosts | |
127.0.0.1 virtualhost.local www.virtualhost.local |
const nodemailer = require('nodemailer'); | |
const transporter = nodemailer.createTransport({ | |
host: 'smtp.zoho.com', | |
port: 465, | |
secure: true, //ssl | |
auth: { | |
user: 'youremail@amitbend.com', | |
pass: 'yourpassword' | |
} | |
}); |
# You should look at the following URL's in order to grasp a solid understanding | |
# of Nginx configuration files in order to fully unleash the power of Nginx. | |
# http://wiki.nginx.org/Pitfalls | |
# http://wiki.nginx.org/QuickStart | |
# http://wiki.nginx.org/Configuration | |
# | |
# Generally, you will want to move this file somewhere, and start with a clean | |
# file but keep this around for reference. Or just disable in sites-enabled. | |
# | |
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples. |
server { | |
# Listen on port 81 | |
listen 81; | |
# Server name being used (exact name, wildcards or regular expression) | |
# server_name phpmyadmin.my; | |
root /usr/share/phpmyadmin; |