Ask HN: Best practices for open source webapp
2 comments
A configurable optional footer with source code link to anywhere.
License in the footer as well (perhaps more difficult to change if the license is copyleft)
As any open source (that want contributors and/or forks), a full readme, a quick start, a contribution guide, a documentation, etc.
License in the footer as well (perhaps more difficult to change if the license is copyleft)
As any open source (that want contributors and/or forks), a full readme, a quick start, a contribution guide, a documentation, etc.
[deleted]
1. Swappable config files (hard to do in frameworks like django where config is code)
2. Can't use proprietary 3rd party apis in core logic or if you do there has to be an open interface to be able to adapt to different vendors (payment_provider_interface vs stripe)
3. Minimize friction for new developer to spin up copy. Meaning if you're forced to rely on multiple services, use something like docker compose to allow a single command to bring up the who command after a git clone.
What are some of your ideas?