benzkji / django-layout Goto Github PK

when creating the virtualenv, right after also do:

pip install --upgrade pip
pip install pip-tools

and move from pip install -r to pip-sync

no more warnings

as not usable, ATM.

for cmsplugin and app template

instead of compass

https://www.liquidlight.co.uk/blog/how-do-i-update-to-gulp-4/

in depth look.

so setting up requires no more manual steps (creating domains and ports on the panel.djangoeurope.com, for example)

that supports python3, but needs quite some refactoring.

use wti unicorn scripts and fabfile

get deployed tag/commit message from remote.

git show --no-patch --oneline | cat
git describe --tags (doesnt work without any tag!)

fab live version
tag: update-3.4-9d-5-g82fb4de
commit: 82fb4de raven fix

for basic lockout / brute force protection

• date based
• frontend editing
• "add in frontend"
• modeltranslation
• providing search index

for reconfiguring default plugins.

• nginx
• uwsgi
• gunicorn + geeve nt
• apache?

deployment/crontab.txt

run('crontab deployment/crontab.txt')

only for live env.

with example. https://github.com/w0rm/gulp-svgstore#options

for example, deactivating users on live system, get db and media, do a big update procedure, put db and media. done.

as startingpoint for djangocms_my plugin template. note to self: melio

security, man.
http://www.linuxjournal.com/node/1001956

from project.live.sh to project-live.sh

drop .my_cnf for mysql, no more insecure history files

SPACES!

ckeditor, migrations

https://github.com/sdispater/poetry
https://poetry.eustace.io/

make both work out of the box. create

• settings
• requirements

for both scenarios.

for example, for when switching from -e installs to production, having a new python version on the server, etc.

• CMS_CACHE_DURATIONS
• middlewares

remove all config files (ngins/uswgi/gunicorn/init scripts/whatever) for that env.

not master

• fabric django deploy tools, no more copy paste!
• cms_app into djangocms-baseplugins/misc (management command, same as "baseplugin_start"

with a "generic" processor, that adds the analytics UA for now, and can be extended easily.

index.html with "under maintainance, we'll be right back".

DRY please: use same for title tag and og:title

• babel
• sass
• autoprefixer or postcss with autoprefix
• fab collectstatic should build and upload assets, so they dont need to be under VCS
• compressor

Bonus

• iconfont
• svgstore

get used to yarn. note to self: meliorat!

so we now if we are on stage or live, during template rendering and in code.

check env.crontab_file

for displaying the fallback, doing some work, then do a normal fab restart

it's not that hard. systemd might be the wrong tool, though. having one systemd/init script for supervisor could be a better solution, as it could also replace cron like things.

note to self: taiga / systemd

https://github.com/torchbox/django-libsass

so it can be easily transferred to baseplugins, if it's worth it. (conf/settings, default naming, etc)