Skip to content

Latest commit

 

History

History
218 lines (154 loc) · 5.46 KB

tips.md

File metadata and controls

218 lines (154 loc) · 5.46 KB
Raw

Notes / Tips

Git

Git setup

git config --global user.name "John Doe"
git config --global user.email [email protected]
  • Under Windows, consider setting core.filemode to false, otherwise you will probably unintentionally commit text files with the executable bit set.
# For Windows ignore the executable bit on files in the working tree
git config --global core.filemode false

# then later if you need to add executable bit to file mode, do
git update-index --chmod=+x file.bat
  • Checking your settings: git config --list

Git Commit message convention

  • How to Write a Git Commit Message
    • https://chris.beams.io/posts/git-commit
    • The seven rules of a great Git commit message
      1. Separate subject from body with a blank line
      2. Limit the subject line to 50 characters
      3. Capitalize first letter of the subject line
      4. Do not end the subject line with a period
      5. Use the imperative mood in the subject line
        • Imperative mood means "spoken or written as if giving a command or instruction", such as: 
          Refactor subsystem X for readability
Remove deprecated methods
Release version 1.0.0
        • A properly formed Git commit "subject line" should always be able to complete the following sentence:
          If applied, this commit will subject line here
      6. Wrap the body at 72 characters
      7. Use the body to explain what and why vs. how

Signing tags and commits

References / Resources

Encryption

  • To encrypt file using a password in a file named file.password using AES-256 and SHA-256 digest
openssl enc -e -aes256 -md sha256 -pass file:file.password -in input.file -out encrypted.sha256.aes256
  • To decrypt file with above settings
openssl enc -d -aes256 -md sha256 -pass file:file.password -in encrypted.sha256.aes256 -out output.file

Nexus Repository

Sonatype Nexus Repository https://www.sonatype.com/nexus-repository-oss

Running Nexus in Docker

=================================================

Setup Persistent data volume

https://hub.docker.com/r/sonatype/nexus3#user-content-persistent-data

docker volume create --name nexus-data

Start Nexus

Default user is admin and the uniquely generated password can be found in the /nexus-data/admin.password file inside the volume. See Persistent Data for information about the volume.

docker run -d -p 8081:8081 --name nexus -v nexus-data:/nexus-data sonatype/nexus3

NOTE: It can take some time (2-3 minutes) for the service to launch in a new container.

  • You can tail the log to determine once Nexus is ready:
docker logs -f nexus
  • To test nexus instance:
curl http://localhost:8081/

curl http://localhost:8081/service/local/status
  • Get initally generated Admin password
  • FYI: this admin.password file is removed after you login and change the admin password.
docker run -it --rm -v nexus-data:/nexus-data alpine cat /nexus-data/admin.password && echo

Stop Nexus with timeout

When stopping, be sure to allow sufficient time for the databases to fully shut down.

docker stop --time=120 nexus

Nginx

service nginx start

# -or-
systemctl start nginx
  • Stop nginx web server
service nginx stop

# -or-
systemctl stop nginx

# -or- (for graceful shutdown)
nginx -s quit

# -or- (for force/fast shutdown)
nginx -s stop
  • Restart nginx web server /usr/local/etc/rc.d/nginx restart
service nginx restart

# -or-
systemctl restart nginx

# -or-
nginx restart
  • Test/Check Nginx configuration file (using -t):
nginx -t -c /path/to/nginx.conf
  • Reload Nginx configuration:
nginx -s reload

# or send SIGHUP signal to nginx process
kill -HUP <nginx-pid>

SSH

Generate secure ssh key

  • Create secure ED25519 SSH key with with 99 KDF rounds:
ssh-keygen -t ed25519 -a 99
  • Get length of private ssh key:
ssh-keygen -lf ~/.ssh/id_rsa

ssh-keygen -lf ~/.ssh/id_ed25519
  • Forward port via ssh:
ssh -L local_port:remote_host:remote_port server