Netnyahoo
Mac용 실질적인 Chromium으로, Arc 사이드바와 Dia 폴리시를 갖추고 계정 없이 무료·오픈소스이며 광고·추적·소송에 면역이다
openpasture는 자동화로 목초 농업을 확장하고, OpenCollar 가상 울타리 목걸이로 가축 이동을 관리합니다
openpasture is scaling pasture-based agriculture through automation. It starts with OpenCollar, a virtual fence collar anyone can build, and grows into software that decides where livestock move each
기타Rust · TypeScriptGitHub @open-pasture온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Run open collars: boundaries, herd moves, data and decisions. Desktop app and self-hosted server.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Runs virtual fence collars, stores their data, analyses it, and decides where the herd goes. One Rust server with the web UI built in. The desktop app runs that server for you.
| macOS app (Apple Silicon and Intel) | openpasture-macos.dmg |
| Server, Linux x64 | openpasture-server-linux-x64.tar.gz |
| Server, Linux arm64 (e.g. Raspberry Pi 4 or 5, 64-bit OS) | openpasture-server-linux-arm64.tar.gz |
| Server, macOS Apple Silicon | openpasture-server-macos-arm64.tar.gz |
| Server, macOS Intel | openpasture-server-macos-x64.tar.gz |
| Docker | ghcr.io/open-pasture/openpasture |
The desktop app is macOS only for now; the server runs on Linux and macOS. Checksums are in
SHA256SUMS on each release, and what
changed in CHANGELOG.md.
mkdir openpasture && cd openpasture
tar xzf ../openpasture-server-linux-x64.tar.gz
./openpasture serve --bind 0.0.0.0 --port 7878
--bind 0.0.0.0 listens on every network the machine is on. Behind a reverse proxy or tunnel,
keep the default 127.0.0.1 instead (see docs/SELF-HOSTING.md).
Open http://<host>:7878. On the machine itself (127.0.0.1) no token is needed. From anywhere
else the app asks for its token once:
./openpasture token
Data lives in OPENPASTURE_DATA_DIR, else the platform data directory; --data-dir DIR
overrides both. It is one SQLite database plus Parquet files, so a copy of the directory is a
backup.
docker run -d --name openpasture -p 7878:7878 -v openpasture:/data ghcr.io/open-pasture/openpasture
docker exec openpasture openpasture token
The image runs as a non-root user and keeps everything in the /data volume.
For a farm: an https address for collars and phones, systemd, backups and upgrades are in
docs/SELF-HOSTING.md; texting and alerts in docs/TEXTING.md.
Until you have a collar, collar-sim, the simulator (in the server tarball, or
simulation/collar-sim), speaks the real collar protocol on a farm of its own:
./collar-sim farm
It starts a throwaway server on port 7991 with "Simulated farm", two paddocks and a herd of
twelve simulated collars, and prints the address. Draw a boundary, send it, and watch the acks
come in and the herd walk into it. The app marks every simulated collar "Simulated", reports
leave them out, and the simulator refuses port 7878 and any data dir with real collars. See
simulation/README.md.
Needs Rust (rustup installs the version pinned in rust-toolchain.toml) and
bun.
cd ui && bun install && bun run build && cd ..
cargo build --release -p op-cli -p collar-sim # target/release/openpasture, collar-sim (the simulator)
cargo test --workspace
bun run desktop:build # the macOS app, Apple Silicon
bun run desktop:release # universal .app and .dmg
The server embeds ui/dist at build time; if it is missing, the build runs bun for you.
Releases are cut by pushing a tag; see docs/RELEASING.md.
docs/SELF-HOSTING.md: running it for a farmdocs/TEXTING.md: Twilio, email, webhook, push, the relaydocs/api/: the APIs, by what you're building (HTTP, live feed, MCP,
fleet, and the collar protocol in opencollar)docs/ARCHITECTURE.md: how it's built; docs/PLAN.md:
the original decisionsdocs/RELEASING.md, CONTRIBUTING.md,
SECURITY.mdThe app is AGPL-3.0. op-protocol and op-geo are Apache-2.0, so collar firmware
and other software can use the protocol and geometry without the AGPL. See NOTICE;
every release lists the third-party code it ships, with licences, in THIRD-PARTY-NOTICES.
Found a security problem? Report it privately: SECURITY.md.