| { | |
| "headers": { | |
| "host": "vidaura.app.n8n.cloud", | |
| "x-request-id": "00bf5a0fd36f4a5dab921fda8d25ef29", | |
| "x-real-ip": "10.40.5.170", | |
| "x-forwarded-for": "10.40.5.170", | |
| "x-forwarded-host": "vidaura.app.n8n.cloud", | |
| "x-forwarded-port": "443", | |
| "x-forwarded-proto": "https", | |
| "x-scheme": "https", |
I'm going to cover a simple, but effective, utility for managing state and transitions (aka workflow). We often need to store the state (status) of a model and it should only be in one state at a time.
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
My personal reverse-i-search: A command line history lookup (because my memory just aint that good)
| ROOT := $(abspath $(dir $(lastword $(MAKEFILE_LIST)))) | |
| HUB := benneic | |
| NAME := myproject | |
| VERSION := latest | |
| TAG := $(HUB)/$(NAME):$(VERSION) | |
| DATE := `date "+%Y-%m-%d"` | |
| # echo output in cyan | |
| define cecho | |
| @tput setaf 6 |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
| GET request (no body): | |
| Connected to 54.83.83.185:80 | |
| HTTP/1.1 200 OK | |
| Content-Length: 40 | |
| Content-Type: text/plain; charset=utf-8 | |
| Date: Tue, 14 Feb 2017 07:05:33 GMT | |
| Connection: keep-alive | |
| Body discarded |
| # | |
| # Set the build number to the current git commit count. | |
| # If we're using the Dev scheme, then we'll suffix the build | |
| # number with the current branch name, to make collisions | |
| # far less likely across feature branches. | |
| # Based on: http://w3facility.info/question/how-do-i-force-xcode-to-rebuild-the-info-plist-file-in-my-project-every-time-i-build-the-project/ | |
| # | |
| # Updated with dSYM handling from http://yellowfeather.co.uk/blog/auto-incrementing-build-number-in-xcode-revisited/ | |
| # |
| ## /v2.2/LocalMeasure/photos | |
| { | |
| "data": [ | |
| { | |
| "id": "645065645556450", | |
| "from": { | |
| "category": "Product/service", | |
| "category_list": [ | |
| { | |
| "id": "2201", |
| # -*- coding: utf-8 -*- | |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| # | |
| # Author: Roman Kalyakin | |
| # | |
| # EC2 to Route53 magic | |
| # | |
| # https://gist.github.com/4449827 | |
| # |