VirtualTam's bookmarks
462 bookmarks found
-
Administration
- https://docs.djangoproject.com/en/2.0/ref/contrib/admin/
- https://docs.djangoproject.com/en/2.0/ref/contrib/admin/admindocs/
Models and Querysets
- https://docs.djangoproject.com/en/2.0/topics/db/models/
- https://docs.djangoproject.com/en/2.0/ref/models/instances/
- https://docs.djangoproject.com/en/2.0/ref/models/fields/
- https://docs.djangoproject.com/en/2.0/topics/db/aggregation/
Static files
User management
- https://docs.djangoproject.com/en/2.0/topics/auth/default/
- https://docs.djangoproject.com/en/2.0/topics/auth/customizing/
- https://docs.djangoproject.com/en/2.0/ref/contrib/auth/
- https://docs.djangoproject.com/en/2.0/ref/settings/#login-redirect-url
URL dispatcher
-
pavdmyt/git-ctm: ⏳ git Commit Time Machine ⌛
2018-02-09 -
- https://www.youtube.com/watch?v=a1rC79DHpmY
- https://www.youtube.com/watch?v=0CGzC_iss-8
- https://github.com/tree-sitter/tree-sitter
- https://github.com/tree-sitter/tree-sitter/tree/master/highlight
- https://siraben.dev/2022/03/01/tree-sitter.html
- https://github.com/tree-sitter/tree-sitter-go
- https://fosdem.org/2018/schedule/event/code_tree_sitter/
-
On the Existence of IT Thingies
2018-01-21 - If it is not managed by SCM, it doesn't exist.
- If it is not covered by tests, it doesn't exist.
- If it cannot be built and deployed in an automated and reproducible way, it doesn't exist.
- If it is not running in production, it doesn't exist.
- If it is not monitored and supervised, it doesn't exist.
Simple, heh?
-
-
Introducing the new SourceForge
2018-01-10 - https://www.reddit.com/r/opensource/comments/7p94h3/introducing_the_new_sourceforge/
- https://www.reddit.com/r/sysadmin/comments/4n3e1s/the_state_of_sourceforge_since_its_acquisition_in/
- https://arstechnica.com/information-technology/2016/06/under-new-management-sourceforge-moves-to-put-badness-in-past/
- https://sourceforge.net/blog/sourceforge-now-scans-all-projects-for-malware-and-displays-warnings-on-downloads/
-
Actors:
- database server / cluster
- load-balanced application servers relying on a database schema with migrations
- reverse proxy
Issue:
- managing database schema migrations
Possible sequence:
- create the database
- run a service that executes database schema migrations
- start application servers
- start the load-balancer / reverse-proxy
Resources:
- https://www.reddit.com/r/docker/comments/2t2pnf/what_are_best_strategies_to_migrate_relational/
- https://softwareengineering.stackexchange.com/questions/357929/db-migration-strategy-for-docker-containers-in-aws-ecs
- https://stackoverflow.com/questions/41592091/run-a-database-migration-command-when-deploying-a-docker-container-to-aws
- https://ltd-keeper.lsst.io/gke-migrations.html
- https://stackoverflow.com/questions/31715239/docker-compose-database-migrations-and-other-pre-post-scripts
- https://stackoverflow.com/questions/38089999/docker-compose-rails-best-practice-to-migrate
- https://stackoverflow.com/questions/37058812/how-best-to-run-one-off-migration-tasks-in-a-kubernetes-cluster
-
Utopian - Rewarding Open Source Contributors
2017-11-24