How to create a self |
您所在的位置:网站首页 › 三人篮球的打法视频教程图解 › How to create a self |
My new favorite way to completely underuse a Makefile? Creating personalized, per-project repository workflow command aliases that you can check in. Can a Makefile improve your DevOps and keep developers happy? How awesome would it be if a new developer working on your project didn’t start out by copying and pasting commands from your README? What if instead of: pip3 install pipenv pipenv shell --python 3.8 pipenv install --dev npm install pre-commit install --install-hooks # look up how to install Framework X... # copy and paste from README... npm run serve… you could just type: make start…and then start working? Making a differenceI use make every day to take the tedium out of common development activities like updating programs, installing dependencies, and testing. To do all this with a Makefile (GNU make), we use Makefile rules and recipes. Similar parallels exist for POSIX flavor make, like Target Rules; here’s a great article on POSIX-compatible Makefiles. Here’s some examples of things we can make easier (sorry): update: ## Do apt upgrade and autoremove sudo apt update && sudo apt upgrade -y sudo apt autoremove -y env: pip3 install pipenv pipenv shell --python 3.8 install: ## Install or update dependencies pipenv install --dev npm install pre-commit install --install-hooks serve: ## Run the local development server hugo serve --enableGitInfo --disableFastRender --environment development initial: update env install serve ## Install tools and start development serverNow we have some command-line aliases that you can check in! Great idea! If you’re wondering what’s up with that weird ## comment syntax, it gets better. A self-documenting MakefileAliases are great, if you remember what they all are and what they do without constantly typing cat Makefile. Naturally, you need a help command: .PHONY: help help: ## Show this help @egrep -h '\s##\s' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}'With a little command-line magic, this egrep command takes the output of MAKEFILE_LIST, sorts it, and uses awk to find strings that follow the ## pattern. It then prints a helpful formatted version of the comments. We’ll put it at the top of the file so it’s the default target. Now to see all our handy shortcuts and what they do, we just run make, or make help: help Show this help initial Install tools and start development server install Install or update dependencies serve Run the local development server update Do apt upgrade and autoremoveNow we have our very own personalized and project-specific CLI tool! The possibilities for improving your DevOps flow with a self-documenting Makefile are almost endless. You can use one to simplify any workflow and produce some very happy developers. Please enjoy the (live!) Makefile I use to manage and develop this Hugo site. I hope it inspires you! My Hugo site Makefile SHELL := /bin/bash .POSIX: .PHONY: help env install upgrade-hugo serve build start initial help: ## Show this help @egrep -h '\s##\s' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' env: pip3 install pipenv shell: ## Enter the virtual environment pipenv shell install: ## Install or update dependencies pipenv install --dev npm install npm install -g markdownlint-cli pre-commit install --install-hooks HUGO_VERSION:=$(shell curl -s https://api.github.com/repos/gohugoio/hugo/releases/latest | grep 'tag_name' | cut -d '"' -f 4 | cut -c 2-) upgrade-hugo: ## Get the latest Hugo mkdir tmp/ && \ cd tmp/ && \ curl -sSL https://github.com/gohugoio/hugo/releases/download/v$(HUGO_VERSION)/hugo_extended_$(HUGO_VERSION)_Linux-64bit.tar.gz | tar -xvzf- && \ sudo mv hugo /usr/local/bin/ && \ cd .. && \ rm -rf tmp/ hugo version dev: ## Run the local development server hugo serve --enableGitInfo --disableFastRender --environment development future: ## Run the local development server in the future hugo serve --enableGitInfo --buildFuture --disableFastRender --environment development build: ## Lock dependencies and build site git pull --recurse-submodules pipenv lock hugo --minify --cleanDestinationDir start: upgrade-hugo serve ## Update Hugo and start development server initial: env install upgrade-hugo serve ## Install tools and start development server |
今日新闻 |
点击排行 |
|
推荐新闻 |
图片新闻 |
|
专题文章 |
CopyRight 2018-2019 实验室设备网 版权所有 win10的实时保护怎么永久关闭 |