Docker.app will complain about incompatible processor, so we will use Docker Machine.
Download Docker for Mac (Docker.app). It contains some binaries that are necessary.
brew install virtualbox docker-machine
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> | |
<dict> | |
<key>Label</key> | |
<string>custom.asdf.postgresql</string> | |
<key>ProgramArguments</key> | |
<array> | |
<string>~/.asdf/shims/postgres</string> | |
<string>-D</string> |
;;; $DOOMDIR/config.el -*- lexical-binding: t; -*- | |
;; Place your private configuration here! Remember, you do not need to run 'doom | |
;; sync' after modifying this file! | |
;; Some functionality uses this to identify you, e.g. GPG configuration, email | |
;; clients, file templates and snippets. It is optional. | |
;; (setq user-full-name "John Doe" | |
;; user-mail-address "[email protected]") |
This uses the native built-in proxy feature in the Telegram app.
The problem is the README in the official TelegramMessenger/MTProxy repo is outdated and fails at multiple points if you try following the steps described. Here's an updated version as of March 2024.
ssh
into the machine:
I hereby claim:
To claim this, I am signing this object:
package org.drools.examples.broker | |
import org.mule.MessageExchangePattern; | |
import org.mule.example.cep.Company | |
import org.mule.example.cep.StockTick | |
global org.mule.module.bpm.MessageService mule; | |
# default dialect for the semantic code will be MVEL | |
dialect "mvel" |
# pip install python-binance | |
from binance.client import Client | |
client = Client(api_key, api_secret) | |
DUST = 0.001 # BTC | |
account = client.get_account() | |
prices = client.get_all_tickers() |
1. Download CSV with rasters you want from USGS. | |
2. Convert CSV to JSON with something like http://www.csvjson.com/ | |
3. Run script with `ruby usgs_downloader.rb path_to_json_file` | |
4. Sit back. | |
5. ??? | |
6. Receive slope analysis |
I made a mistake to naming some components, I don't want to erase it and create again, the problem is, I need to rename the files by hand, it's a boring task, and maybe in the future I will get the same issue, to make me the life easier I developed the following snippet, you should use it if you have the same problem.
#!/usr/bin/env bash
# purpose: rename files, in same path