• 4 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: September 5th, 2024

help-circle
  • I use fireflyiii and paperlees-ngx. I did exactly what you plan to do with concourse-ci instead of n8n. I’m not extracting as much data from the receipts yet - was too lazy to implement it.

    I basically have a receipts document type on paperless and a “imported” tag. Querying for all receipts which don’t have the imported tag and then creating transactions in firefly with a reference to the paperless document. The imported transaction gets two tags one to denote that it was automatically imported and one that gets removed once i manually verified the import.

    Since I only scan my receipts with my phone the ocr job of paperless doesnt do too good of a job so I cant really automate more than that yet, maybe I’ll get a scanner for that.

    If you like I can share my concourse pipeline.






  • All the important login information should just be present somewhere in your home folder. If you back that up and restore it later you should be fine, no need to save the dropbox binary.

    If that is no option and you only want to back up dropbox files and nothing else follow the instructions below (I can’t guarantee that they will work, but they should):

    Back up the whole system, if something goes wrong you can at least restore to a working state. Read the instructions at least once completely before following them.

    Look at the documentation for dropbox to see which files are relevant and need backing up. Its the Dropbox folder with all the files, but will probably be some folders/files in your $HOME too, which store login information. Lets hope that they don’t store some metadata there that will invalidate the config if it’s running on a different machine (to prevent what you are trying to do).

    If there is no documentation, you can stop dropbox completely. Look for dropbox processes that don’t get stopped when you stop the GUI with something like pgrep -f -i dropbox.

    Once you are sure all dropbox processes are stopped run inotifywait -r -m ~. That command wont exit unless you stop it by issuing ^C. It will list all filesystem events in your home directory. Now start dropbox and see which files it accesses, those are the files you need to back up. It will probably be one or more whole directories in ~/.config and ~/.local.

    Add those files to a tar archive using something like this: tar cvJf dropbox_config.tar.xz [list of folders...]. Savre the resulting tar file somewhere else, reinstall and extract it using tar xvJf dropbox_config.tar.xz. Take care to run those commands from the same directory.

    The dropbox login secrets might also be stored in your system’s keyring, if you are using GNOME, then that will be GNOME Keyring. Open your system’s credential manager and look for stuff related to dropbox. Look for instructions on how to back up and restore those secets. I don’t use that often enough to be able to give you more detailed instructions right now though.

    References

    Edit:

    • backups
    • keyring







  • I use something like this:

    #!/bin/bash
    
    set -euo pipefail
    URLS=(
        'https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/'
        'https://addons.mozilla.org/en-US/firefox/addon/privacy-badger17/'
        'https://addons.mozilla.org/en-US/firefox/addon/passff/'
        'https://addons.mozilla.org/en-US/firefox/addon/copy-plaintext/'
        'https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-for-firefox/'
        'https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher/'
        'https://addons.mozilla.org/en-US/firefox/addon/clearurls/'
        'https://addons.mozilla.org/en-US/firefox/addon/temporary-containers/'
        'https://addons.mozilla.org/en-US/firefox/addon/consent-o-matic/'
    )
    
    DOWNLOAD_BASE_URL='https://addons.mozilla.org/firefox/downloads/latest'
    _="${FIREFOX:=firefox}"
    _="${DST:=/usr/lib/$FIREFOX/browser/extensions}"
    
    if [ $UID -eq 0 ]; then
        SUDO=
    else
        SUDO=sudo
    fi
    
    
    download_links=()
    for url in "${URLS[@]}"; do
        package_name="$(sed 's_/$__' <<< "$url" | awk -F/ '{print $NF}')"
        download_links+=("$DOWNLOAD_BASE_URL/$package_name/addon-$package_name.xpi")
    done
    
    workdir="$(mktemp --directory)"
    cd "$workdir"
    for url in "${download_links[@]}"; do
        curl -OL "$url"
    done
    
    for ext in *.xpi; do
        ext_id="$(unzip -p "$ext" 'manifest.json' | jq -r '(if .browser_specific_settings then .browser_specific_settings else .applications end).gecko.id')"
        target="$DST/$ext_id.xpi"
        echo "$ext -> $target"
        $SUDO install -Dm644 "$ext" "$target"
    done
    

    That doesn’t handle the extension config though.


  • redxef@feddit.orgtoMemes@sopuli.xyzOff topic
    link
    fedilink
    arrow-up
    11
    ·
    6 months ago

    I’m sure that is a good price for the soundbar, but speaking for myself it’s too big, I don’t have the space for it, as I imagine many others do too. It isn’t too cheap either, imo.

    But that is really not the point. Not everyone is a giant movie geek, they just want to be able to understand what is being said.



  • Ich bin sehr zufrieden mit meinem Pixel 4a mit LineageOS.

    Ich hab den LineageOS build vom microG Projekt genommen, da das die wichtigen play services für die Banking Apps, etc spooft. Blöd ist nur, dass viele dann noch Safety Net abchecken - also hab ich das Handy dann noch gerootet und einen Spoofer dafür eingerichtet.

    Also die Route ist nur was für Tüftler, wenn ich ehrlich bin. Man muss sich auch aufschreiben was man wie installiert hat beim OS aufsetzen, weil die Android-Versions Upgrades macht nicht die Updater App (minor Upgeades gehen darüber schon), die muss man selber wieder flashen, und wenns nicht genau so passiert wie bei der erst-installation kanns sein, dass dein Handy auf Werkseinstellungen zurück gesetzt ist.

    Wenn ich jetzt ein neues Handy anschaffen würde, dann eines der neueren Pixel Geräte und GrapheneOS, das ist sicherer und ein smootherer Ride als Lineage.


  • No, there is no reason really afaik. Firmware updates can be installed with the desktop software, but they can also be installed either OTA or by dropping the update file onto the sdcard. The Kobo devices are really easy to hack, but I have heard that newer ones come with secure boot.

    I only ever tried adding custom software onto their devices, like KOReader and Syncthing, I never switched out the whole OS.

    I’ve had and modded both the Kobo Clara and Kobo Clara Colour and never used their desktop software or even created an account to log in on the device.