{"id":16847400,"url":"https://github.com/indygreg/zippylog","last_synced_at":"2025-04-11T06:34:01.159Z","repository":{"id":989189,"uuid":"795523","full_name":"indygreg/zippylog","owner":"indygreg","description":"Structured Message Bus, Store, and Event Processing System","archived":false,"fork":false,"pushed_at":"2012-09-06T23:54:21.000Z","size":3912,"stargazers_count":15,"open_issues_count":0,"forks_count":1,"subscribers_count":5,"default_branch":"master","last_synced_at":"2025-03-25T04:27:45.731Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"C++","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"sahat/hackathon-starter","license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/indygreg.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2010-07-24T19:50:46.000Z","updated_at":"2023-09-08T16:27:12.000Z","dependencies_parsed_at":"2022-08-16T11:45:15.484Z","dependency_job_id":null,"html_url":"https://github.com/indygreg/zippylog","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/indygreg%2Fzippylog","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/indygreg%2Fzippylog/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/indygreg%2Fzippylog/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/indygreg%2Fzippylog/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/indygreg","download_url":"https://codeload.github.com/indygreg/zippylog/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248357615,"owners_count":21090398,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-13T13:07:47.576Z","updated_at":"2025-04-11T06:34:01.136Z","avatar_url":"https://github.com/indygreg.png","language":"C++","funding_links":[],"categories":[],"sub_categories":[],"readme":"# zippylog - A Fast and Efficient Message Bus and Store\n\nThis document is targeted to end users wishing to install zippylog on a system.\n\nFor details about the zippylog project, including why you may want to use it,\nvisit the [project wiki](http://wiki.github.com/indygreg/zippylog/).\n\nAdditional, more technical documentation, is stored next to the code it describes in the *doc/* directory of the Git repository.\n\n## System Requirements\n\nTo run, zippylog requires:\n\n* Protocol Buffers 2.3.0 or later\n* ZeroMQ 2.0.10 or later\n* Lua 5.1 (or any distribution conforming to the C API)\n\nTo build zippylog and generate message classes, you'll need:\n\n* Python 2.6 or later\n* CMake (Linux)\n* Visual Studio 2008 or later (Windows)\n\n## Installing\n\nInstructions for installing zippylog are in the *doc/* directory. See the various -development.md files.\n\n## Defining Messages\n\nNext, you'll need to create your domain-specific Protocol Buffer message\ndefinitions for the messages you wish to record.\n\nStart by creating a directory to hold your definitions.\n\n`mkdir ~/zippylog-messages`\n\n`cd ~/zippylog-messages`\n\nYou'll create .proto files in this directory.\n\nThe directory structure in this directory determines the namespace of\nmessages. The first directory level is the message namespace. This likely\ncorresponds with your company or organization name. i.e. if you are the\n_ACME_ company, you'll probably want to create an _acme_ directory at\nthe root.\n\nUnder your namespace directory, create additional directory layers as are\nnecessary.\n\nAt any directory, create .proto files containing your message definitions.\nThe name of the file will form a final namespace member.\n\nFor small organizations with limited amounts of message types, you may want\na flat namespace:\n\n* /acme/webapp.proto\n* /acme/db.proto\n\nOr, if there are many message types per application, you may wish to group them\nadditionally:\n\n* /acme/webapp/errors.proto\n* /acme/webapp/billing.proto\n* /acme/webapp/performance.proto\n\nFor larger organizations, you may wish to add some corporate hierarchy:\n\n* /acme/operations/router_stats.proto\n* /acme/operations/system_stats.proto\n* /acme/sales/purchase_order.proto\n\nThe protocol buffer\n[Language Guide](http://code.google.com/apis/protocolbuffers/docs/proto.html)\nis the definitive source for creating .proto files.\n\nOnce you have defined your messages, you'll need to run _zippylog_compile_ to\ngenerate bindings to zippylog.\n\n\u003e zippylog_compile ~/zippylog-messages ~/zippylog-generated\n\nLike the message source directory, you'll likely want to have the output\ndirectory under version control. That way, in case you do something silly,\nyou can easily revert changes.\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Findygreg%2Fzippylog","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Findygreg%2Fzippylog","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Findygreg%2Fzippylog/lists"}