Entries Categorized as 'Technology'
Author:
erics, August 10th, 2020
For more information about Tagging in GIT, please visit: https://git-scm.com/book/en/v2/Git-Basics-Tagging Add an Annotated Tag:
|
|
git tag -a v1.0.0 -m "Software version 1.0.0" git show v1.0.0 |
Add a Lightweight Tag:
|
|
git tag v1.0.1 git show v1.0.1 |
Show all tags:
Push all tags:
Add a Tag Later:
|
|
git log --pretty=oneline git tag v1.0.2 5370c8da4095fefad7476fa1c226a309dd00a9f7 git tag -a v1.0.2 5370c8da4095fefad7476fa1c226a309dd00a9f7 fatal: tag 'v1.0.2' already exists git tag -d v1.0.2 Deleted tag 'v1.0.2' (was 5370c8d) git tag -a v1.0.2 5370c8da4095fefad7476fa1c226a309dd00a9f7 git push origin --tags |
Use a Tag:
|
|
git checkout -b {new branch name} {tag name} git checkout -b v1.0.2-from-tag v1.0.2 |
Categories: How-To's, Technology Tags: git, howto, Tag, Tags, tips
| 
No comments
Author:
erics, August 6th, 2020
Disable NOW in vim:
To disable auto-comments permanently, add the following line to ~/.vimrc:
|
|
autocmd FileType * setlocal formatoptions-=c formatoptions-=r formatoptions-=o |
To see the current settings:
Visit https://vim.fandom.com/wiki/Disable_automatic_comment_insertion for more information!
Categories: How-To's, Technology Tags: Auto-Comment, Comment, Comment Insertion, Comments, Disable, howto, Stop, tips, turn off, vim
| No comments
Author:
erics, August 3rd, 2020
|
|
convert BIA_Plate_Number_Checklist_1-20000.pdf[0-819] new.pdf |
Categories: How-To's, Technology Tags: convert, howto, ImageMagick, PDF, Remove, tips
| No comments
Author:
erics, July 22nd, 2020
dscacheutil -flushcache System Preferences -> Network -> Advanced -> DNS -> Add 1.1.1.1, 8.8.4.4 and 8.8.8.8 at the top. If they are already there, CHANGE THE ORDER!
Categories: How-To's, Technology Tags: 10.14, Cache, dig, DNS, dscacheutil, Flush, flushcache, howto, lookup, MacOS, Mojave, Ping, tips, util
| No comments
Author:
erics, July 16th, 2020
Problem: Running npm i gave me an UNABLE_TO_GET_ISSUER_CERT_LOCALLY error Solution:
|
|
npm config set registry http://registry.npmjs.org/ |
Full Error text:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
npm WARN package.json beat-cors-server@1.0.0 No repository field. npm http GET https://registry.npmjs.org/express npm http GET https://registry.npmjs.org/request npm http GET https://registry.npmjs.org/express npm http GET https://registry.npmjs.org/request npm http GET https://registry.npmjs.org/express npm http GET https://registry.npmjs.org/request npm ERR! Error: UNABLE_TO_GET_ISSUER_CERT_LOCALLY npm ERR! at SecurePair.<anonymous> (tls.js:1430:32) npm ERR! at SecurePair.emit (events.js:92:17) npm ERR! at SecurePair.maybeInitFinished (tls.js:1029:10) npm ERR! at CleartextStream.read [as _read] (tls.js:521:13) npm ERR! at CleartextStream.Readable.read (_stream_readable.js:341:10) npm ERR! at EncryptedStream.write [as _write] (tls.js:418:25) npm ERR! at doWrite (_stream_writable.js:226:10) npm ERR! at writeOrBuffer (_stream_writable.js:216:5) npm ERR! at EncryptedStream.Writable.write (_stream_writable.js:183:11) npm ERR! at write (_stream_readable.js:602:24) npm ERR! at flow (_stream_readable.js:611:7) npm ERR! at Socket.pipeOnReadable (_stream_readable.js:643:5) npm ERR! If you need help, you may report this log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <npm-@googlegroups.com> npm ERR! System Linux 4.14.181-108.257.amzn1.x86_64 npm ERR! command "node" "/usr/bin/npm" "i" npm ERR! cwd /volumes/data/www/dashboard/corsproxy npm ERR! node -v v0.10.48 npm ERR! npm -v 1.3.6 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /volumes/data/www/dashboard/corsproxy/npm-debug.log npm ERR! not ok code 0 |
Categories: How-To's, Technology Tags: howto, node, node.js, npm, npm i, tips, UNABLE_TO_GET_ISSUER_CERT_LOCALLY
| No comments
Author:
erics, July 15th, 2020
|
|
sudo chgrp grafana /etc/letsencrypt/archive/www.yourdomain.com/privkey1.pem sudo chmod g+r /etc/letsencrypt/archive/www.yourdomain.com/privkey1.pem sudo vi /etc/grafana/grafana.ini sudo service grafana-server restart |
|
|
[server] # Protocol (http, https, socket) ;protocol = http protocol = https # https certs & key file ;cert_file = ;cert_key = cert_file = /etc/letsencrypt/archive/www.yourdomain.com/fullchain1.pem cert_key = /etc/letsencrypt/archive/www.yourdomain.com/privkey1.pem |
Categories: How-To's, Technology Tags: cert, certificate, Certs, chgrp, chmod, Enable, Existing, Grafana, Grafana Server, howto, https, LetsEncrypt, Restart, service, ssl, sudo, tips
| No comments
Author:
erics, July 15th, 2020
|
|
sudo vi /etc/grafana/grafana.ini sudo service grafana-server restart |
|
|
#################################### Anonymous Auth ###################### [auth.anonymous] # enable anonymous access ;enabled = false enabled = true # specify organization name that should be used for unauthenticated users ;org_name = Main Org. org_name = yourGrafanaOrgNameHere |
Categories: How-To's, Technology Tags: /etc/grafana/grafana.ini, Access, Anonymous, Anonymous Access, Enable, Enable Anonymous Access, Grafana, Grafana Server, grafana.ini, howto, INI, Restart, sudo, Yips
| No comments
Author:
erics, July 15th, 2020
To render a panel image, you must install the Grafana Image Renderer plugin.
|
|
sudo grafana-cli plugins install grafana-image-renderer sudo service grafana-server restart |
Categories: How-To's, Technology Tags: Direct, Direct Link, Grafana, Grafana Server, howto, Image, Link, Panel, Panel Image, Render, Rendering, Server, tips
| No comments
Author:
erics, July 11th, 2020
|
|
find wordpress/wp-content/plugins -type d -exec chmod 2775 {} \; find wordpress/wp-content/plugins -type f -exec chmod 664 {} \; find wordpress/wp-content/themes -type d -exec chmod 2775 {} \; find wordpress/wp-content/themes -type f -exec chmod 664 {} \; find wordpress/wp-content/upgrade -type d -exec chmod 2775 {} \; find wordpress/wp-content/upgrade -type f -exec chmod 664 {} \; |
Categories: How-To's, Technology Tags: chmod, howto, Permissions, tips, WordPress
| No comments
Author:
erics, July 9th, 2020
shell$ git log | head -1 commit a203e1bd04718bff10a3df4a3389c493c97c0432 Use the commit string as the last argument to the git revert command: shell$ git revert -m 1 a203e1bd04718bff10a3df4a3389c493c97c0432
Categories: How-To's, Technology Tags: commit, git, git merge, git revert, howto, last, Last Commit, Merge, Mistake, Revert, Revert Commit, revert merge, tips
| No comments
