| from django.template.loader import select_template | |
| class MultisitePage(Page): | |
| """ | |
| Page model to be used for mutli-site projects. | |
| """ | |
| class Meta: | |
| abstract = True |
| pipx | |
| pipenv | |
| ipython | |
| notebook | |
| numpy | |
| scipy | |
| pandas | |
| matplotlib | |
| altair | |
| seaborn |
The goal of this workflow is to couple vue-cli to Django, in a transparent way in dev and in prod. The hot-reload is active in the backend as well as in the frontend, and the frontend is accessed through Django, from the index page ;)
Note: We also use the router's historical mode, for a more professional integration.
Note²: Do not forget to build the vue-cli project for production!
| # import * from pygame | |
| import env | |
| from random import * | |
| class World: | |
| X_MIN = 0 | |
| X_MAX = env.MAP_WIDTH | |
| Y_MIN = 0 | |
| Y_MAX = env.MAP_HEIGHT |
| """ | |
| Two things are wrong with Django's default `SECRET_KEY` system: | |
| 1. It is not random but pseudo-random | |
| 2. It saves and displays the SECRET_KEY in `settings.py` | |
| This snippet | |
| 1. uses `SystemRandom()` instead to generate a random key | |
| 2. saves a local `secret.txt` |
| <?php | |
| // Tell PHP that we're using UTF-8 strings until the end of the script | |
| mb_internal_encoding('UTF-8'); | |
| // Tell PHP that we'll be outputting UTF-8 to the browser | |
| mb_http_output('UTF-8'); | |
| // Our UTF-8 test string | |
| $string = 'Êl síla erin lû e-govaned vîn.'; | |