Sometimes I want to execute a python callback with some args on the command line, but i get frustrated that it always requires to wrap my command in a wrapper of some sort. Then, I want to do generic CRUD operations from the command line in my automation tool. Clilabs unfrustrates me.

Get started:

$ pip install clilabs $ clilabs clilabs automates python callables parametered calls.

Things starting with - will arrive in clilabs.context.

djcli is the package , a new CLI under design phase, it is a simple python package, that provides a command with name djcli, to do more with Django on the CLI:

$ pip install djcli

find the content for this variable in your project manage.py

$ export DJANGO_SETTINGS_MODULE=your.settings

you will probably run this from your directory parent to manage.py:

$ djcli create auth.user username=pony is_superuser=1

i just checked and chpasswd command in django supports only interactive

$ djcli chpasswd /path/to/password username=pony

“Extreme DevOps” screenshot, where you see branchname == lastbuildjobname, designed for dynamic environments, demonstrates auto-deploy an environment per push on a subdomain with the branch name. From betagouv/MRS#636, with PlayLabs, currently in Alpha stage.

https://blog.risingstack.com/yarn-vs-npm-node-js-package-managers/

How Facebook spies on Yarn users.

Quick version of the previous article on playlabs

$ playlabs Playlabs: the obscene ansible distribution.

Init your ssh user with your key and secure sshd and passwordless sudo:

playlabs init root@1.2.3.4
# all options are ansible options are proxied
playlabs init @somehost --ask-become-pass

Now your user can install roles:

playlabs install docker,firewall,nginx @somehost

And deploy a project, examples:

playlabs @somehost deploy image=betagouv/mrs:master
playlabs @somehost deploy
    image=betagouv/mrs:master
    plugins=postgres,django,uwsgi
    backup_password=foo
    prefix=ybs
    instance=hack
    env.SECRET_KEY=itsnotasecret
playlabs @somehost deploy
    prefix=testenv
    instance=$CI_BRANCH
    image=$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA

If you have that work, creating an inventory is the way to move on, wether you want to version configuration, add a deploy user for your CI, configure a secret backup password, add ssh-keys …:

From baremetal to deploying docker images on a PaaS in one command ?

PlayLabs is the result of a refactor of playbooks we’ve had in production for a while to acheive hackable docker-based PaaS. The refactor was designed to be Open Source, almost there to beta.

PlayLabs combines simple ansible patterns with packaged roles to create a docker orchestrated paas to prototype products for development to production.

PlayLabs does not deal with HA, for HA you will need to do the ansible plugins yourself, or use kubernetes … but until then, PlayLabs do everything else, even configure your own sentry or kubernetes servers ! Or install things like sendmail and netdata for alerts and more … Detail here of the current development:

This is a plain advertisement for two excellent test utils maintained by YourLabs:

• django-dbdiff
• django-responsediff

If you’re volunteering on a project, and that there are many newbie contributors - who turn out to be militants with a high determination - then you definitively want to check out these apps as they will highly facilitate your volunteering in a project as sole professional dev.

https://git.yourlabs.org/oss/django-collectdir

Want to split your react components accross your django apps or anything like that ? Try django-collectdir, which implements a instant realtime django-app directory watcher with beautiful colors for development !

https://github.com/containers/buildah

Build docker images without docker.

https://github.com/cfenollosa/os-tutorial