josh
watchman
josh | watchman | |
---|---|---|
21 | 31 | |
1,335 | 12,275 | |
3.8% | 0.5% | |
7.5 | 9.0 | |
4 days ago | 7 days ago | |
Rust | C++ | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
josh
- GitHub – josh-project/josh: Just One Single History
-
Debian Git Monorepo
Why use submodules when you can properly vendor the upstream git, and export/import commits without breaking hashes on either side?
https://github.com/josh-project/josh
We've been using josh at TVL for years and it's just amazing.
- Josh: Just One Single History
- Just One Single History
- Metahead – An enterprise-grade, Git-based metarepo
-
PyPy has moved to Git, GitHub
Scalar explicitly does not implement the virtualized filesystem the OP is referring to. The original Git VFS for Windows that Microsoft designed did in fact do this, but as your second link notes, Microsoft abandoned that in favor of Scalar's totally different design which explicitly was about scaling repositories without filesystem virtualization.
There's a bunch of related features they added to Git to achieve scalability without virtualization. Those are all useful and Scalar is a welcome addition. But the need for a virtual filesystem layer for large-scale repositories is still a very real one. There are also some limitations that aren't ideal; for example Git's partial clones IIRC can only be used as a "cone" applied to the original filesystem hierarchy. More generalized designs would allow mapping any arbitrary paths in the original repository to any other path in the virtual checkout. Tools like Josh can do this today with existing Git repositories[1]. That helps you get even sparser and smaller checkouts.
The Git for Windows that was referenced isn't even that big at 300GB, by the way. Game studios regularly have repositories that exist at multi-terabyte size, and they have also converged on similar virtualization solutions. For example, Destiny 2 uses a "virtual file synchronization" layer called VirtualSync[2] that reduced the working size of their checkouts by over 98%, multiple terabytes of savings per person. And in a twist of fate, VirtualSync was implemented thanks to a feature called "ProjFS" that Microsoft added to Windows... which was motivated originally by the Git VFS for Windows they abandoned!
[1] https://github.com/josh-project/josh
[2] https://www.gdcvault.com/play/1027699/Virtual-Sync-Terabytes...
- Just One Single History – combine the advantages of monorepos with multirepos
-
Kubernetes Broke Git
Good overview, I know these sorts of pains well. Lots of hard questions and few definitive wins/right answers. How to organize a massive repository out in the open is still an open question. On that note, recently, I've been experimenting with this project called josh, which basically is like 'git subtree on extreme steroids, functioning as a git proxy':
https://josh-project.github.io/josh/
It basically lets you unify/view many repositories as a single one, or equivalent to split a mono-repo into smaller sized units of work for CI, specific teams, etc. It's bidirectional, so you push and pull from josh and everything goes into a single linear history in the mono repo. And because it's bidirectional, people in the mono-repo can still do things like make large-scale atomic changes across all sub-repositories, and those get reflected.
Josh currently isn't suitable for a lot of workloads due to various reasons (authentication is one that stands out), but it's actually the first tool I have seen that manages to offer BitKeeper-like "subtrees" that work really well, at scale, for large repos and teams. It requires some care to make sure "sub-trees" can be usable units of work, but it was one of the best features of BK in my opinion and really great for people doing one-off contributions, or isolating trees/changes to specific developers.
I'd be interested to know if there are other open alternatives to this. It's a nice point in the design space between solutions like "integrate with the filesystem layer to do sparse clones" or "just split up the repos."
-
What Comes After Git
With regard to repo composition, I have been following this project: https://github.com/josh-project/josh
watchman
- Watchman – A File Watching Service
-
Dev Container for React Native with Expo
postCreateCommand This section permit to execute a command after the build of the container. I've used this command to execute a script to install Expo and other dependencies like watchman
- Using Bun.js as a Bundler
- How To Monitor a Folder On Startup
-
changedetection for file shares
Facebook open source product: https://github.com/facebook/watchman to get notified when configuration, file or other change
- [Media] OnChange: CLI utility to automatically run commands on file change (details in comments)
-
Any else using Meta's née Facebook's Watchman service?
Facebook Meta's Watchman Service looks very useful for watching for changes in files and directories to kick off automation. Still, there seem to be a bunch of gotchas with it that only come to light after trying to mess with it. The docs seem lacking, the Python library needs to be updated, and even the installation on non-Ubuntu or Red Hat distros requires a rebuild, which has been somewhat problematic given the build tools. Also, no official Docker container.
- Show HN: I built a tool to get instant test results (
- Watchman: A File Watching Service
-
Watchman: Execute a command when something changes
Not to be confused with Facebook’s file watch daemon, which does the same sort of thing but is more complicated. There’s a bunch of tools that integrate Facebook’s watchman for more efficient change tracking.
https://facebook.github.io/watchman/
What are some alternatives?
josh - Just One Single History
wireguard-ui - Wireguard web interface
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
watchexec - Executes commands in response to file modifications
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
nvim-lsp-ts-utils - Utilities to improve the TypeScript development experience for Neovim's built-in LSP client.
josh - Just One Single History [Moved to: https://github.com/josh-project/josh]
lush.nvim - Create Neovim themes with real-time feedback, export anywhere.
git-branchless - High-velocity, monorepo-scale workflow for Git
Lsyncd - Lsyncd (Live Syncing Daemon) synchronizes local directories with remote targets
VFSForGit - Virtual File System for Git: Enable Git at Enterprise Scale
go-git - A highly extensible Git implementation in pure Go.