Implementing a basic plugin architecture shouldn't be a complicated task. The solution described here is working but you still have to import every plugin (inheriting from the base class).
This is my solution:
$ tree
Kshitij Chawla kchawla-pi
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| """Script to get all files touched by PRs.""" | |
| import shutil | |
| from pathlib import Path | |
| from warnings import warn | |
| import requests | |
| from rich import print |
dorneanu
/ plugin_architecture.md
Last active
June 22, 2024 21:54
Python: Implement basic plugin architecture with Python and importlib
ojengwa
/ docker-compose2aws
Last active
January 18, 2024 17:58
Set by step guide on deploying your docker containers to AWS using docker-compose and docker-machine
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Deploy to AWS using docker-machine and docker-compose | |
| ## 1. Prepare your machine | |
| Please follow this steps: | |
| 1.1 Install docker in your localhost. [Installation link](https://docs.docker.com/engine/installation/) | |
| 1.2 Install docker-machine in your localhost. [Installation link](https://docs.docker.com/compose/install/) | |
| 1.3 Install docker-compose in your localhost. [Installation link](https://docs.docker.com/machine/install-machine/) | |
| 1.4 Create an account in AWS (skip this step if you already have one). [AWS](https://aws.amazon.com/) |
itod
/ split_keyboards.md
Last active
June 12, 2024 12:08
Every "split" mechanical keyboard currently being sold that I know of
-
Kinesis Freestyle (Terrible key switches. Mushy and un-lovable)
-
Kinesis Freestyle Edge (Traditional layout with too many keys, mech switches, proably too big to be tented easily/properly)
-
Matias Ergo Pro (Looks pretty great. Have not tried.)
-
ErgoDox Kit (Currently, my everyday keyboard. Can buy pre-assembled on eBay.)
-
ErgoDox EZ (Prolly the best option for most people.)
dropmeaword
/ browser_history.md
Last active
April 5, 2024 17:37
Playing around with Chrome's history
Unless you are using Safari on OSX, most browsers will have some kind of free plugin that you can use to export the browser's history. So that's probably the easiest way. The harder way, which seems to be what Safari wants is a bit more hacky but it will also work for other browsers. Turns out that most of them, including Safari, have their history saved in some kind of sqlite database file somewhere in your home directory.
The OSX Finder cheats a little bit and doesn't show us all the files that actually exist on our drive. It tries to protect us from ourselves by hiding some system and application-specific files. You can work around this by either using the terminal (my preferred method) or by using the Cmd+Shft+G in Finder.
Once you locate the file containing the browser's history, copy it to make a backup just in case we screw up.