noxasaxon

Learning Rust

Getting Started + Installation | Cheat Sheet

Table of Contents

1. How Do I Start Learning Rust?!
2. Ok, I Think I Know The Basics But How Do I Get Better?!
3. Rustlang Tooling
4. Helpful References Throughout Your Journey
5. The Rust Community
6. Recommended (but not free) Books & Courses

ruanbekker

version: "3.7"

services:
  # https://docs.gitea.io/en-us/install-with-docker/
  gitea:
    image: gitea/gitea:1.12.4
    # https://hub.docker.com/r/gitea/gitea/tags
    container_name: gitea
    environment:
      - APP_NAME=Gitea

DanBurkhardt

# Install "sshpass" on macOS. 
# 
# - sshpass allows you to easily automate password entry 
# prompts for ssh sessions.
# 
# Don't mess around with terminal if you 
# don't know what any of this means, please.
# Evaluate for learning purposes at your own risk.
# 
# Licensed under MIT. See below.

israeljrs

ffmpeg

ffmpeg is a fast video and audio converter that can also grab from a live audio/video source.

Standard usage

Getting help and information

• -h show all options
• -h(elp) topic show help
• -version show version
• -formats show available formats

mmazzarolo

import { useRef } from "react";
import { Animated, Easing } from "react-native";

export const useAnimation = function(initialValue: number = 0) {
  const endValue = initialValue === 0 ? 1 : 0;
  const animationValueRef = useRef<Animated.Value>(new Animated.Value(initialValue));

  const setup = (config: Partial<Animated.TimingAnimationConfig> = {}) =>
    Animated.timing(animationValueRef.current, {
      toValue: endValue,

DeanPDX

Windows 10 - Using Git Bash With TMUX

Why Not Use WSL?

I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve, dotnet watch run, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.

That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull on my "windows" project folder, and do a production build there

W1R3D-Code

[Unit]
Description=SonarQube service
After=syslog.target network.target

[Service]
Type=forking

ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start
ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop

sebastianrothbucher

This is how you can conver the react docs to a .ePub / Kindle (.mobi) file to read in an eReader (or eReader app):

• Make sure you have Pandoc available (on a Mac, it can be installed by brew install pandoc via Homebrew)
• Checkout or download master from the React docs repo [https://github.com/reactjs/reactjs.org]
• go to content/docs
• run the following commands in a shell (builds one markdown in order of navigation):

echo '' > ALL.md
for i in $(cat nav.yml | grep 'id:' | awk -F:  '{print$2}')
do

hashrock

import React from "react";
import ReactDOM from "react-dom";

const Circle = () => {
  const [position, setPosition] = React.useState({
    x: 100,
    y: 100,
    active: false,
    offset: { }
  });

allenyllee

#!/bin/bash

# install qemu utils
sudo apt install qemu-utils

# install nbd client
sudo apt install nbd-client