GitLab Web-IDE screenshot

Some screenshots from a backoffice using CRUDLFA+

https://github.com/indietyp/django-automated-logging

Pretty cool alternative to django.contrib.admin.LogEntry

Still finishing CRUDLFA+ framework for Django 2.0, see example esponsive detail page for BetaGouv with MaterializeCSS.

https://media.ccc.de/v/33c3-8044-what_could_possibly_go_wrong_with_insert_x86_instruction_here

Long live Chaos Communication Congress

http://danielhnyk.cz/deploying-scalable-django-app-on-kubernetes/

Apparently, browser testing stack for CRUDLFA+ based on CircleCI, SauceLabs, NightWatchJS, TypeScript, is getting operational. All configurations are Open Source. Have a beautiful day

Any kind of dev workflow that’s not as efficient as this one is considered deprecated / obsolete by YourLabs. Have a beautiful day

Keith Braithwaite

Collected by highly respected hacker Uriel (RIP) on harmful.cat-v.org

It’s a curious thing about our industry: not only do we not learn from our mistakes, we also don’t learn from our successes.

CRUDLFA+ is an expirement (read: pre-alpha state) of what Django could be if:

• generic views provided templates and javascript for a rich experience out of the box,
• class based views leveraged OOP a bit more to add DRY goodness,
• leveraged externals apps from the Django ecosystem.

Let’s compare it side by side. Consider this simple model:

class Email(models.Model):
    email = models.EmailField()
    caisse = models.ForeignKey('Caisse', on_delete=models.CASCADE)

    def __str__(self):
        return self.email

This admin.py:

class EmailAdmin(admin.ModelAdmin):
    list_display = ('email', 'caisse')


admin.site.register(Email, EmailAdmin)

Ported to CRUDLFA+, in the case where we only want a list view, becomes (crudlfap.py):