Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
D
DHFS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
DragonHive
WyvernWorks
Experiments
DHFS
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
9d1eee265eb3d0fa3d44f3625abb4f9ed03c2e83
Select Git revision
Selected
9d1eee265eb3d0fa3d44f3625abb4f9ed03c2e83
Branches
1
main
default
protected
2 results
Begin with the selected commit
Created with Raphaël 2.2.0
17
Jun
21
May
5
Mar
Update README.md
main
main
adding the config.yml for the fuseclient as example
Update README.md
added example template of the syncscript's config.json
a sync script that will keep a local server in sync with one or more remote servers
A fuse client in python written by chatgpt- not checked for errors
Update README.md
fix name
define config that specifies directories to store data in
significant improvements and changes, should support enough for basic fuse API now
Add API explanation
Updated v1.js; ". In modern versions of Node.js, the fs.exists method is deprecated, and it's recommended to use fs.access instead. Also, you're right that we can make this more asynchronous by using the fs.promises API. Let's rewrite the previous code to address these points"
added an initial version which can down/upload files and fetch metadata from the /files/ endpoint
tried to make a blob storage with an s3-like API for storing and fetching files and metadata
generated based on the previous core.py, by the chat session that was still open
added server.js which sends the journal and upon request sends files, just like the python version, although seems oversimplified by gpt4
added client.js, which replicates the log actions locally similar to how the python did it
made gpt4 translate it to nodejs
added server.py, which looks at the journal.log and sends updates to the clients, and when a client requests a file, sends over the file, including a hash, so the client can verify the file integrity on that side.
added the client.py, which handles every action that the server sends it, and fetches the related file every time a write action happens on it. No connection error handling yet.
added the journal parser, which also acts as a library for the client and server to generate events from the journal updates
added core.py which just acts as a transparent fuse filesystem and logs every action to a journal
basic distributed fuse based filesystem
Add new directory
added experiments directory which will contain a bunch of chatgpt and other experiments to create a multi node filesystem
Wrote the start of an actual relevant readme file
Initial commit
Loading