Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)That's it!
| class QuerySetDoubleIteration(Exception): | |
| "A QuerySet was iterated over twice, you probably want to list() it." | |
| pass | |
| # "Skinny" here means we use iterator by default, rather than | |
| # ballooning in memory. | |
| class SkinnyManager(Manager): | |
| def get_query_set(self): | |
| return SkinnyQuerySet(self.model, using=self._db) |
| 1) backup production database: | |
| heroku pgbackups:capture --expire --remote production | |
| 2) obtain url string to backup from step 1: | |
| heroku pgbackups:url --app production_app_name --remote production_app_branch_name | |
| 3) transfer backup from production to staging app: | |
| heroku pgbackups:restore DATABASE 'production_app_backup_url_string_from_step_2' --app production_app_name --app staging_app_branch_name |
| heroku addons:add pgbackups --remote staging | |
| heroku addons:add pgbackups --remote production | |
| heroku pgbackups:capture --remote production | |
| heroku pgbackups:restore DATABASE `heroku pgbackups:url --remote production` --remote staging |
| // Lefalet shortcuts for common tile providers - is it worth adding such 1.5kb to Leaflet core? | |
| L.TileLayer.Common = L.TileLayer.extend({ | |
| initialize: function (options) { | |
| L.TileLayer.prototype.initialize.call(this, this.url, options); | |
| } | |
| }); | |
| (function () { | |
Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)That's it!
| var myApp = angular.module('myApp').config(function($httpProvider) { | |
| $httpProvider.defaults.headers.post['X-CSRFToken'] = $('input[name=csrfmiddlewaretoken]').val(); | |
| }); |
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.
| "scripts": { | |
| "dev": "node .dev/webpack.dev.server.js", | |
| "dev-prod": "node .dev/webpack.dev.server.js --production", | |
| "build": "rimraf ./dist && webpack --config .dev/webpack.config.production.js --colors", | |
| }, | |
| "devDependencies": { | |
| "@babel/core": "7.0.0-beta.38", | |
| "@babel/plugin-proposal-class-properties": "7.0.0-beta.38", | |
| "@babel/plugin-proposal-decorators": "7.0.0-beta.38", | |
| "@babel/plugin-transform-classes": "7.0.0-beta.38", |
| command | usage | |
|---|---|---|
| git init | Creates an empty Git repository in the specified directory. | |
| git clone <repository name> | Clones a repository located at <repository name> onto your local machine. | |
| git add <directory> | Stages only the specified changes for the next commit. Replace <directory> with a <file> to change a specific file. | |
| git add . | Stages new files and modifications without deletions | |
| git add -A | Stages all changes | |
| git add -all | Equivalent to git add -A | |
| git add -u | Stages modifications and deletions without adding new files | |
| git add --update | Equivalent to git add -u | |
| git commit -m ”<message>” | Commits the staged snapshot. replace <message> with the commit message. |