www.mechaelephant.com
setup
| www.mechaelephant.com | setup | |
|---|---|---|
| 3 | 2 | |
| 1 | 4 | |
| - | - | |
| 8.8 | 3.2 | |
| 19 days ago | about 2 years ago | |
| JavaScript | Jinja | |
| - | 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.
www.mechaelephant.com
- Ask HN: Tips to get started on my own server
- A search engine in 80 lines of Python
-
My Second Brain – Zettelkasten
For me, the idea is sound but the implementation always seems so cumbersome. I want something that separates the data from the display as much as possible, has an easy 'note taking' and has an easy install. One problem I always encounter is that if the interface to add notes has too much friction, I stop using it pretty quickly.
Anyway, so I created something over the weekend called 'notenox' [0]. It creates a a JSON file of relevant information, one JSON file per note, with keywords and a "special" keyword prefix called a 'title' that mimics how I've actually been taking notes (email, so the 'title' mimics an email thread). For display, I consolidate all JSON files into a single JSON file and then have it loaded into the browser with some Javascript to group by title or keyword, along with doing all cross referencing and counting on the client end.
Creating notes is done through the command line, because that's a common way I interact with my computer, with different options to create titles, links, keywords, etc. I'm sure there are many different Zettelkasten implementations out there but they always seem so clunky and cumbersome. It's not hard, so the simple use case should be simple, nor should it proprietary or locked behind a SaaS.
You can see my personal notes in action, if you like [1] (sorry, not mobile friendly!).
[0] https://github.com/abetusk/www.mechaelephant.com/tree/releas...
[1] https://mechaelephant.com/notenox
setup
-
Ask HN: Tips to get started on my own server
- Come up with ways to start and stop services and such
In the end, as you start to see patterns for all this, you will find it beneficial to script everything in some way so that you can easily reuse patterns and lessons on other servers and apps.
I tend to use Ansible for this, and here is a concrete example of all sorts of things you might find interesting: https://github.com/scancer-org/setup
This sets up a server, locks it down, adds a python app with a worker set and so on: https://github.com/scancer-org/setup
Good luck on your learning journey!
-
How I made Python/Django Apps deploy themselves
Use Ansible. Here is an example of one of my Django apps’ setup scripts: https://github.com/scancer-org/setup
What are some alternatives?
anystyle - Fast citation reference parsing
dokku-dashboard - A GUI for Dokku hosted on Dokku
djangitos
dokku-scheduler-kubernetes - Scheduler plugin for deploying applications to kubernetes
appliku_start - Starter Template for Django apps
django-project-template - The Django project template I use, for installation with django-admin.
redbeat - RedBeat is a Celery Beat Scheduler that stores the scheduled tasks and runtime metadata in Redis.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS