mitchross

ARG ARM
ARG ARCH=${ARM:+arm32v7}
FROM ${ARCH:-amd64}/python:3.11-slim-bullseye as base

FROM base as builder
ENV PYTHONUNBUFFERED=1
ARG ARM
ARG LIB_ARCH=${ARM:+arm}
ARG MTX_ARCH=${ARM:+armv7}
ARG FFMPEG_ARCH=${ARM:+armv7l}

mitchross

 => [wheels 7/7] RUN pip3 wheel --wheel-dir=/wheels -r requirements-whee  57.7s
 => CACHED [deps 1/4] RUN --mount=type=bind,source=docker/install_deps.sh  0.0s
 => [deps 2/4] RUN --mount=type=bind,from=wheels,source=/wheels,target=/  30.0s
 => [deps 3/4] COPY --from=deps-rootfs / /                                 0.7s
 => [deps 4/4] RUN ldconfig                                                1.7s
 => [devcontainer 1/5] COPY docker/fake_frigate_run /etc/s6-overlay/s6-rc  0.2s
 => [devcontainer 2/5] RUN apt-get update     && apt-get install wget -y  47.2s
 => [devcontainer 3/5] WORKDIR /workspace/frigate                          0.3s
 => [devcontainer 4/5] RUN apt-get update     && apt-get install make -y  11.6s
[+] Building 1245.1s (59/60)                                                    

mitchross

The long answer

There are other application-specific content types, and there are other content types based on JSON that are also registered with IANA with their own identifiers.

While the “json” identifier alone would have been unambiguous, the “application” identifier does not serve to disambiguate “json” subtypes. In fact, the answer to this question is within the definition of the “Accept” HTTP header alone, but let’s go through the rest of the specs first, for some context.

HTTP

In RFC 7231 (2014)[1], or Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, one of a set of documents that defines HTTP/1.1, you can find this about these headers (in page 8):

mitchross

ere is a basic Python script using the Flask web framework that calls the OpenCV REST API to report new CVE vulnerabilities and displays the results on a web dashboard:

Copy code
from flask import Flask, render_template
import requests

app = Flask(__name__)

@app.route("/")
def index():

mitchross

  wyze-bridge:
        container_name: wyze-bridge
        restart: unless-stopped
        privileged: true
        networks:
        - web
        labels:
        - "traefik.enable=true"
        - "traefik.http.routers.wyze-bridge.rule=Host(`wyze.lab.xxx.me`)"
        - "traefik.http.routers.wyze-bridge.entrypoints=https"

mitchross

apiVersion: apps/v1
kind: Deployment
metadata:
  name: wyze-bridge
  labels:
    app: wyze-bridge
spec:
  replicas: 1
  selector:
    matchLabels:

mitchross

Rsync 

rsync -avh "/mnt/remotes/DESKTOP-E098GF7_ed/Desktop/Data" "/mnt/user/data" (destination)

Whats the difference between
/source/folder & /source/folder/
When there is / at the end it will copy all the contents of whats in the folder.
But not the folder itself.
Without the / it will copy the whole folder and its contents

mitchross

<?xml version="1.0"?>
<Container version="2">
  <Name>docker-wyze-bridge</Name>
  <Repository>mrlt8/wyze-bridge</Repository>
  <Registry>https://hub.docker.com/r/mrlt8/wyze-bridge</Registry>
  <Network>bridge</Network>
  <MyIP/>
  <Shell>sh</Shell>
  <Privileged>false</Privileged>
  <Support>https://github.com/mrlt8/docker-wyze-bridge</Support>

mitchross

0. pull latest v9 branch. run "make -j 4 aarch64_frigate"
1. Open VS Code. Click run as container pop up
2. in VS dev container, run "python3 -m frigate"
3. Open new terminal in vs dev container and run "cd web && npm install", then npm start
4.  Might need to CHOWN the debug directory to user not root. If ls -all shows root owns "debug" folder than CHOWN / Chmod it to current user. 

mitchross

import React, {Component, useState} from 'react';
import { Button, Collapse, Nav, Navbar, NavbarBrand, NavbarToggler, NavItem, NavLink } from 'reactstrap';
import { Link } from 'react-router-dom';

const NavBar = (props) => {
    //
    // constructor(props) {
    //     super(props);
    //     this.state = {isOpen: false};
    //     this.toggle = this.toggle.bind(this);