3 ms·
I recently wrote one: https://github.com/epilys/sic https://github.com/epilys/sic
by epilys 5y ago
I recently wrote one: https://github.com/epilys/sic https://github.com/epilys/sic
- emptysongglass 5y agoI am loving this, thanks for sharing. My only request would be for a publicly hosted image so I can easily selfhost for my own little campfire community.
- epilys 5y agoHmm I might add one thanks for the suggestion. I don't use containers for this since it's just python WSGI on apache2 (no database image required since it's sqlite3)
- e12e 5y agoThanks for sharing, I missed your earlier "show hn": https://news.ycombinator.com/item?id=28086637 https://news.ycombinator.com/item?id=28086637 As someone not too familiar with Django, this looks like a nice codebase :) But am I right that there are no tests?
- epilys 5y agoThank you! Indeed there are no tests. I'm not familiar with testing in Django or web apps in general but I want to add some once I figure out what and how I should be testing.
- e12e 5y agoWell, in my limited experience, the best way to do testing is to start with tests first (TDD/BDD) - and the second best, when you've started, and have no tests - is to start from a bug: someone reports a real bug, in your real system - and you try and write a test that's failing in such a way, that when you alter the system to fix the bug, the test will pass. Typically the first test will be quite painful - you might have to install a testing dependency, possibly re-work some code to allow for testing etc. But then, the next test should be a little easier. And after a few bugs and tests, you might find that for your next feature, you can somewhat easily start with a failing test. /unsolicted_advice
- goodpoint 5y agoPython, AGPL and without JS? Excellent!