[{"_1":2,"_152":-5,"_153":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_131":132},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":130},"canonicalUrl","https://hub.docker.com/r/cosme/zero/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","cosme","reponame","zero","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-05-08T21:30:30.274386Z","description","","is_private","last_updated","2019-05-08T21:38:28.347536Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",3865,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\n \n

Zero Server

Zero configuration web framework.

\n\n

\n\n

\n \n $\"Join$ \n \n

\n\n---\n\n**Zero** is a web framework to simplify modern web development. It allows you to build your application without worrying about package management or routing. It's as simple as writing your code in a mix of [Node.js](docs/nodejs/README.md), [React](docs/react/README.md), [HTML](docs/html/README.md), [MDX](docs/mdx/README.md), [Vue](docs/vue/README.md), [Python](docs/python/README.md), and [static files](docs/static/README.md) and putting them all in a folder. Zero will serve them all. Zero abstracts the usual project configuration for routing, bundling, and transpiling to make it easier to get started.\n\n_An example project with different types of pages, all in one folder:_\n\n![A basic mono-repo](https://raw.githubusercontent.com/remoteinterview/zero/master/docs/images/header.gif \"A basic mono-repo\")\n\n## Features\n\n**Auto Configuration**: Your project folder doesn't require config files. You just place your code and it's automatically compiled, bundled and served.\n\n**File-system Based Routing**: If your code resides in `./api/login.js` it's exposed at `http:///api/login`. Inspired by good ol' PHP days.\n\n**Auto Dependency Resolution**: If a file does `require('underscore')`, it is automatically installed and resolved. You can always create your own `package.json` file to install a specific version of a package.\n\n**Multiple Languages**: Zero is designed to support code written in many languages all under a single project. Imagine this:\n\n1. Exposing your Tensorflow model as a python API.\n2. Using React pages to consume it.\n3. Writing the user login code in Node.js.\n4. Your landing pages in a mix of HTML or Markdown/MDX.\n\nAll under a single project folder as a single web application.\n\n**Improved Error Handling**: Each endpoint run in their own process. So if `/api/login` crashes for some reason, it doesn't affect `/chatroom` page or `/api/chat` API. Crashed endpoints are restarted automatically when the next user visits them.\n\n## Installation\n\nYou can install `zero` globally by:\n\n```sh\nnpm install -g zero\n```\n\n## Getting Started\n\nLet's start by making a website that tells us server time.\n\nFirst we need to create an API endpoint in Node.js to tell us time in JSON.\n\nCreate a new folder and add a new file `time.js` in that folder. In this file, export a function that accepts `Request` and `Response` objects ([like Express](https://expressjs.com/en/4x/api.html#res)):\n\n```js\n// time.js\nconst moment = require(\"moment\");\n\nmodule.exports = (req, res) => {\n var time = moment().format(\"LT\"); // 11:51 AM\n res.send({ time: time });\n};\n```\n\nOnce saved, you can `cd` into that folder and start the server like this:\n\n```sh\nzero\n```\n\nRunning this command will automatically install any dependencies (like _momentjs_ here) and start the web server.\n\nOpen this URL in the browser: [`http://localhost:3000/time`](http://localhost:3000/time)\n\nYou just created an API endpoint 🎉:\n\n![Time API](docs/images/timeapi.png?raw=true \"Time API\")\n\nKeep the server running. Now let's consume our API from a React page, create a new file `index.jsx` and add the following code:\n\n```jsx\n// index.jsx\nimport React from \"react\";\n\nexport default class extends React.Component {\n static async getInitialProps() {\n var json = await fetch(\"/time\").then(resp => resp.json());\n return { time: json.time };\n }\n\n render() {\n return

Current time is: {this.props.time}

;\n }\n}\n```\n\nThis is a standard React component. With one additional hook for initial data population:\n\n`getInitialProps` is an `async` static method which is called by `zero` when the page loads. This method can return a plain object which populates `props`.\n\nNow go to this URL: `http://localhost:3000/` and you should see the current server time rendered by React while `fetch`-ing an API endpoint you created earlier:\n\n![Time In React](docs/images/timejsx.png?raw=true \"Time In React\")\n\n`zero` automatically bundles your code and supports server-side rendering. You don't need to fiddle with webpack anymore.\n\nThat's it! You just created a web application.\n\n## Routing\n\n### File-system Based Routing\n\nZero serves routes based on file structure. If you write a function that resides in `./api/login.js` it's exposed at `http:///api/login`. Similarly if you put a React page under `./about.jsx` it will be served at `http:///about`\n\n### Route Rewrites\n\nSometimes you would want to change `/user?id=luke` to `/user/luke`. To cater this type of routes, **all requests sent to a route that doesn't exist are passed on to the closest parent function**.\n\nSo if you visit `/user/luke` and there is no `./user/luke.js` but there is `./user.js`. Zero will send the request to `/user` and set `req.params` to `['luke']`. Code for this:\n\n```js\n// user.js\nmodule.exports = function(req, res) {\n console.log(req.params); // ['luke'] when user visits /user/luke\n res.send({ params: req.params });\n};\n```\n\nAnother example: if you visit `/user/luke/messages`. Zero will also forward this to `./user.js` and set `req.params` to `['luke', 'messages']`\n\n## Supported Languages\n\n- [Node.js](docs/nodejs/README.md) _(JavaScript & TypeScript)_\n- [React](docs/react/README.md) _(JavaScript & TypeScript)_\n- [HTML](docs/html/README.md)\n- [Markdown / MDX](docs/mdx/README.md)\n- [Vue](docs/vue/README.md)\n- [Python](docs/python/README.md)\n\n## Auto Dependency Resolution\n\nIf a file does `require('underscore')`, the latest version of that package is automatically installed from NPM and resolved.\n\nBut sometimes you want to use a specific version or a dependency from a private repository. You can do that by creating a `package.json` in your project folder and adding dependencies to it. Zero will install those versions instead.\n\nExample (package.json):\n\n```json\n{\n \"name\": \"myapp\",\n \"dependencies\": {\n \"underscore\": \"^1.4.0\",\n \"private_ui_pkg\": \"git+https://github.com/user/repo.git\"\n }\n}\n```\n\n## .zeroignore file\n\nBy default, Zero compiles and serves all files in your project. But most of the time, you don't want to expose a certain file or folder. You can add `.zeroignore` file to prevent Zero from serving that file as a valid route.\n\n### Example\n\nIn a project with following structure:\n\n```\n- project/\n-- components/\n-- api/\n-- index.jsx\n```\n\nYou probably don't want to expose `components` directory. To do this, you can create `.zeroignore` file with the following text:\n\n```\ncomponents\n```\n\nThis will prevent your users from accessing `/components` path directly.\n\n## Running on Cloud\n\nA Zero app is a regular Node.js server. But zero doesn't create `package.json` in your project folder. For most clouds (Heroku, EC2, etc) you probably need `package.json`. You can create one similar to this:\n\n```json\n{\n \"name\": \"my-zero-app\",\n \"scripts\": {\n \"dev\": \"zero\",\n \"build\": \"zero build\",\n \"start\": \"NODE_ENV=production zero\"\n },\n \"dependencies\": {\n \"zero\": \"latest\"\n }\n}\n```\n\n- We add dependency `zero`, so the cloud builder can install `zero` on your server.\n- Add a `\"start\"` command and also set `NODE_ENV` to `production` so zero generates minified builds and disabled HMR etc.\n- Add a `\"build\"` command to pre-build all files to speed up cold boots. Don't forget to run `npm run build` in your build step (in your Dockerfile, `heroku-postbuild`, etc)\n- If your cloud has an option to set environment variables / config variables (to store secrets, API keys, etc), these variables are automatically passed to your code and can be accessed as you normally would. In node, using `process.env.MY_SECRET`. You should never commit your local `.env` file to your code.\n\nAfter this, you can follow the instructions from your cloud provider for deploying a Node.js app.\n\n### Heroku Buildpack\n\nWe provide an official [Buildpack for Heroku](https://github.com/remoteinterview/zero-heroku-buildpack). If you are deploying on Heroku, this is the easiest way.\n\n### Changing Server's Port\n\nBy default zero runs on port `3000`. You can change this by setting the `PORT` environment variable, like this: `PORT=8080 zero`\n\n### Running with Docker\n\nHere is a basic `Dockerfile` you can add to your zero application to Docker-ize it:\n\n```dockerfile\nFROM node:alpine\n\n\n# Install dependencies via apk\nRUN apk update && apk upgrade \\\n && apk add --no-cache python g++ make \\\n && rm -rf /var/cache/apk/*\n\n# Install zero globally\nRUN npm install --quiet --no-progress --unsafe-perm -g zero\n\n# Add current folder to /app\nADD . /app\n\n# Run zero in production mode\nENV NODE_ENV production\n\n# Expose port\nENV PORT 80\nEXPOSE 80\n\nWORKDIR /app\n\nCMD [\"zero\"]\n```\n\n## Contributing\n\nPlease see our [CONTRIBUTING.md](CONTRIBUTING.md)\n\n## License\n\nZero is [Apache-2.0 licensed](LICENSE.md).\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",171679666,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",1964302,"full_size",171671627,"id",54979732,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:b974bacc50e346919da2bedac67ae718be553bafa505fd6272cba9d342fcb5bd","features","last_pulled","2026-09-17T00:17:37.387058076Z","last_pushed","2019-05-08T21:38:28Z","os","linux","os_features","os_version","size","variant","2019-05-08T21:38:28.010473Z","last_updater","last_updater_username","media_type","latest","repository",7089632,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":133,"_140":141,"_129":150,"_151":11},{"_36":134,"_38":135,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":136,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":137,"_75":11,"_76":139,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":138},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_142":60,"_143":-5,"_144":-5,"_145":146},"count","next","previous","results",[147],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":148,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[149],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

cosme/zero

Tags for cosme/zero