python-architecture-linter
docker-flask-example
python-architecture-linter | docker-flask-example | |
---|---|---|
2 | 31 | |
11 | 643 | |
- | - | |
0.0 | 8.2 | |
over 1 year ago | 17 days ago | |
Python | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
python-architecture-linter
- How boring should your team be
-
Navigate ASTs with x-path-like queries
>I've found myself manually writing code for finding things in python's AST but a tool like this would be much more succinct
Wow, I also am writing a tool for finding things in the Python AST: https://github.com/Incognito/python-architecture-linter
It does other things too, but one of the key features is reading the AST. It's a bit of a prototype but if you want to jam together on a project I'd be open to it.
docker-flask-example
-
We Have to Talk About Flask
I've been maintaining my Build a SAAS App with Flask video course[0] for 8 years. It has gone from pre-1.0 to 2.3 and has been recorded twice with tons of incremental updates added over the years to keep things current.
In my opinion tutorial creators should pin their versions so that anyone taking the course or going through the tutorial will have a working version that matches the video or written material.
I'm all for keeping things up to date and do update things every few months but rolling updates don't tend to work well for tutorials because sometimes a minor version requires a code change or covering new concepts. As a tutorial consumer it's frustrating when the content doesn't match the source code unless it's nothing but a version bump.
I've held off upgrading Flask to 3.0 and Python 3.12 due to these open issues with 3rd party dependencies https://github.com/nickjj/docker-flask-example/issues/17.
[0]: https://buildasaasappwithflask.com/
-
Working with Docker Containers Made Easy with the Dexec Bash Script
I usually end up with project specific "run" scripts which are just shell scripts so I can do things like `./run shell` to drop into the shell of a container, or `./run rails db:migrate` to run a command in a container.
Here's a few project specific examples. They all have similar run scripts:
- https://github.com/nickjj/docker-flask-example
- Looking to use Docker & Docker Compose in production and need advice.
-
Docker Compose Examples
There's a lot of "tool" selections in that repo.
If anyone is looking for ready to go web app examples aimed at both development and production, I maintain:
- https://github.com/nickjj/docker-flask-example
-
starter project?
Personally I maintain https://github.com/nickjj/docker-flask-example. There's also https://github.com/nickjj/build-a-saas-app-with-flask if you want more opinions.
-
Act: Run your GitHub Actions locally
This is what I do except I use a shell script instead of a Makefile.
A working example of this is at: https://github.com/nickjj/docker-flask-example/blob/912388f3...
Those ./run ci:XXX commands are in: https://github.com/nickjj/docker-flask-example/blob/912388f3...
I like it because if CI ever happens to be down I can still run that shell script locally.
- docker-compose file repository?
-
How boring should your team be
> I've encountered a code written in the 12factor style of using environment variables for configuration, and in that particular case there was no validation nor documentation of the configuration options. Is this typical?
I don't know about typical, it comes down to how your team values the code they write.
You can have a .env.example file commit to version control which explains every option in as much or as little detail as you'd like. For my own personal projects, I tend to document this file like this https://github.com/nickjj/docker-flask-example/blob/main/.en....
-
The Unreasonable Effectiveness of Makefiles
I did this for a while but make isn't well suited for this use case. What I end up doing is have a shell script with a bunch of functions in it. Functions automatically becomes a callable a command (with a way to make private functions if you want) with pretty much no boiler plate.
The benefit of this is it's just shell scripting so you can use shell features like $@ to pass args to another command or easily source and deal with env vars.
I've written about this process at https://nickjanetakis.com/blog/replacing-make-with-a-shell-s... and an example file is here https://github.com/nickjj/docker-flask-example/blob/main/run.
-
Flask boilerplate project recommendation?
There's: https://github.com/nickjj/docker-flask-example
What are some alternatives?
architecture_decision_record - Architecture decision record (ADR) examples for software planning, IT leadership, and template documentation
mangum - AWS Lambda support for ASGI applications
architecture-decision
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
rfcs - Specifications for Interledger and related protocols
build-a-saas-app-with-flask - Learn how to build a production ready web app with Flask and Docker.
Flake8 - flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
postgres-and-redis - 🗄 PostgreSQL + Redis. Self-Hosted. Docker + Traefik + HTTPS.
IronFunctions - IronFunctions - the serverless microservices platform by
cookiecutter-flask - A flask template with Bootstrap, asset bundling+minification with webpack, starter templates, and registration/authentication. For use with cookiecutter.
python-architecture-linter-demo - Demo of python-architecture-linter using a definition and CLI
full-stack-fastapi-template - Full stack, modern web application template. Using FastAPI, React, SQLModel, PostgreSQL, Docker, GitHub Actions, automatic HTTPS and more.