- Create a directory for project
- Copy
docker-compose.yml
- Create
/extensions
in project directory. - Run
docker-compose up -d
''' Tool for FUNCTION and FUNCTION. ''' | |
# Better description of thing. | |
import os | |
import click | |
# used to tell Click that -h is shorthand for help | |
CONTEXT_SETTINGS = dict(help_option_names=['-h', '--help']) | |
JPG = $(wildcard Orig/*.JPG) | |
PDF = $(patsubst Orig/%.JPG,%.pdf,$(JPG)) | |
CONCAT = "/System/Library/Automator/Combine PDF Pages.action/Contents/Resources/join.py" | |
.PHONY: help clean all convert concat | |
.DEFAULT : | |
@$(MAKE) help |
Any GitHub wiki can be cloned by appending wiki.git
to the repo url, so the clone url for
the repo https://myorg/myrepo/
is: [email protected]/myorg/myrepo.wiki.git
(for ssh) or https://github.com/my/myrepo.wiki.git
(for https).
You make edits, and commit and push your changes, like any normal repo.
You need to clone the wiki repo and edit it on your system.
`--> mkdir ~/Documents/Projets/Kivy | |
`--> cd ~/Documents/Projets/Kivy | |
`--> virtualenv -p /usr/local/bin/python3 venv | |
Running virtualenv with interpreter /usr/local/bin/python3 | |
Using base prefix '/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6' | |
New python executable in /Users/aperus/Documents/Projets/Kivy/venv/bin/python3.6 | |
Also creating executable in /Users/aperus/Documents/Projets/Kivy/venv/bin/python | |
Installing setuptools, pip, wheel...done. |
#!/bin/sh | |
# | |
# Runs during git flow release start | |
# | |
# Positional arguments: | |
# $1 Version | |
# | |
# Return VERSION - When VERSION is returned empty gitflow | |
# will stop as the version is necessary | |
# |
# connect to tty on Docker for Mac VM | |
screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty | |
# disconnect that session but leave it open in background | |
Ctrl-a d | |
# list that session that's still running in background | |
screen -ls | |
# reconnect to that session (don't open a new one, that won't work and 2nd tty will give you garbled screen) |
GitHub supports several lightweight markup languages for documentation; the most popular ones (generally, not just at GitHub) are Markdown and reStructuredText. Markdown is sometimes considered easier to use, and is often preferred when the purpose is simply to generate HTML. On the other hand, reStructuredText is more extensible and powerful, with native support (not just embedded HTML) for tables, as well as things like automatic generation of tables of contents.
from kivy.config import Config | |
Config.set('graphics', 'width', '320') | |
Config.set('graphics', 'height', '480') | |
from kivy.app import App | |
from kivy.lang import Builder | |
from kivy.uix.widget import Widget | |
from kivy.uix.settings import SettingsWithNoMenu | |
import json |
This is all based on the [alpha release][1].
From the built-in help system:
For many settings TextMate will look for a .tm_properties file in the current folder and in any parent folders (up to the user’s home folder).
These are simple setting = value listings where the value is a format string in which other variables can be referenced.