[{"_1":2,"_165":-5,"_166":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_140":141},"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},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_83":-5,"_84":85,"_133":-5,"_134":11,"_135":17,"_136":11,"_137":-5,"_138":139},"canonicalUrl","https://hub.docker.com/r/fischerscode/parse-server/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","fischerscode","reponame","parse-server","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_37":38,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":50,"_52":30,"_27":28,"_53":54,"_55":39,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":69,"_74":11,"_75":76,"_80":28,"_81":82},"categories",[],"content_types",[39],"image","date_registered","2021-04-15T14:48:33.396064Z","description","","is_private","last_updated","2021-04-15T14:55:17.588645Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[51],"application/vnd.docker.container.image.v1+json","name","pull_count",294,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\n $\"Parse$ \n \n

\n\n

\n Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.\n

\n\n\n

\n $\"Follow$ \n \n $\"Build$ \n \n $\"Coverage$ \n $\"npm$ \n $\"Join$ \n $\"Snyk$ \n

\n\n

\n $\"MongoDB$ \n $\"MongoDB$ \n

\n\n

Our Sponsors

Our backers and sponsors help to ensure the quality and timely development of the Parse Platform.

🥉 Bronze Sponsors

\n\n

\n $\"Backers$ \n $\"Sponsors$ \n

\n
\n\nParse Server works with the Express web application framework. It can be added to existing web applications, or run by itself.\n\nThe full documentation for Parse Server is available in the [wiki](https://github.com/parse-community/parse-server/wiki). The [Parse Server guide](http://docs.parseplatform.org/parse-server/guide/) is a good place to get started. An [API reference](http://parseplatform.org/parse-server/api/) and [Cloud Code guide](https://docs.parseplatform.org/cloudcode/guide/) are also available. If you're interested in developing for Parse Server, the [Development guide](http://docs.parseplatform.org/parse-server/guide/#development-guide) will help you get set up.\n\n- [Getting Started](#getting-started)\n - [Running Parse Server](#running-parse-server)\n - [Locally](#locally)\n - [Docker](#inside-a-docker-container)\n - [Saving an Object](#saving-your-first-object)\n - [Connect an SDK](#connect-your-app-to-parse-server)\n - [Running elsewhere](#running-parse-server-elsewhere)\n - [Sample Application](#parse-server-sample-application)\n - [Parse Server + Express](#parse-server--express)\n - [Configuration](#configuration)\n - [Basic Options](#basic-options)\n - [Client Key Options](#client-key-options)\n - [Email Verification & Password Reset](#email-verification-and-password-reset)\n - [Custom Pages](#custom-pages)\n - [Using Environment Variables](#using-environment-variables-to-configure-parse-server)\n - [Available Adapters](#available-adapters)\n - [Configuring File Adapters](#configuring-file-adapters)\n - [Logging](#logging)\n- [Live Queries](#live-queries)\n- [GraphQL](#graphql)\n- [Upgrading to 3.0.0](#upgrading-to-300)\n- [Support](#support)\n- [Ride the Bleeding Edge](#want-to-ride-the-bleeding-edge)\n- [Contributing](#contributing)\n- [Contributors](#contributors)\n- [Sponsors](#sponsors)\n- [Backers](#backers)\n\n\n# Getting Started\n\nThe fastest and easiest way to get started is to run MongoDB and Parse Server locally.\n\n## Running Parse Server\n\nBefore you start make sure you have installed:\n\n- [NodeJS](https://www.npmjs.com/) that includes `npm`\n- [MongoDB](https://www.mongodb.com/) or [PostgreSQL](https://www.postgresql.org/)(with [PostGIS](https://postgis.net) 2.2.0 or higher)\n- Optionally [Docker](https://www.docker.com/)\n\n### Locally\n```bash\n$ npm install -g parse-server mongodb-runner\n$ mongodb-runner start\n$ parse-server --appId APPLICATION_ID --masterKey MASTER_KEY --databaseURI mongodb://localhost/test\n```\n***Note:*** *If installation with* `-g` *fails due to permission problems* (`npm ERR! code 'EACCES'`), *please refer to [this link](https://docs.npmjs.com/getting-started/fixing-npm-permissions).*\n\n\n### Inside a Docker container\n\n```bash\n$ git clone https://github.com/parse-community/parse-server\n$ cd parse-server\n$ docker build --tag parse-server .\n$ docker run --name my-mongo -d mongo\n```\n\n#### Running the Parse Server Image\n\n```bash\n$ docker run --name my-parse-server -v config-vol:/parse-server/config -p 1337:1337 --link my-mongo:mongo -d parse-server --appId APPLICATION_ID --masterKey MASTER_KEY --databaseURI mongodb://mongo/test\n```\n\n***Note:*** *If you want to use [Cloud Code](https://docs.parseplatform.org/cloudcode/guide/) feature, please add `-v cloud-code-vol:/parse-server/cloud --cloud /parse-server/cloud/main.js` to command above. Make sure the `main.js` file is available in the `cloud-code-vol` directory before run this command. Otherwise, an error will occur.*\n\nYou can use any arbitrary string as your application id and master key. These will be used by your clients to authenticate with the Parse Server.\n\nThat's it! You are now running a standalone version of Parse Server on your machine.\n\n**Using a remote MongoDB?** Pass the `--databaseURI DATABASE_URI` parameter when starting `parse-server`. Learn more about configuring Parse Server [here](#configuration). For a full list of available options, run `parse-server --help`.\n\n### Saving your first object\n\nNow that you're running Parse Server, it is time to save your first object. We'll use the [REST API](http://docs.parseplatform.org/rest/guide), but you can easily do the same using any of the [Parse SDKs](http://parseplatform.org/#sdks). Run the following:\n\n```bash\n$ curl -X POST \\\n-H \"X-Parse-Application-Id: APPLICATION_ID\" \\\n-H \"Content-Type: application/json\" \\\n-d '{\"score\":1337,\"playerName\":\"Sean Plott\",\"cheatMode\":false}' \\\nhttp://localhost:1337/parse/classes/GameScore\n```\n\nYou should get a response similar to this:\n\n```js\n{\n \"objectId\": \"2ntvSpRGIK\",\n \"createdAt\": \"2016-03-11T23:51:48.050Z\"\n}\n```\n\nYou can now retrieve this object directly (make sure to replace `2ntvSpRGIK` with the actual `objectId` you received when the object was created):\n\n```bash\n$ curl -X GET \\\n -H \"X-Parse-Application-Id: APPLICATION_ID\" \\\n http://localhost:1337/parse/classes/GameScore/2ntvSpRGIK\n```\n```json\n// Response\n{\n \"objectId\": \"2ntvSpRGIK\",\n \"score\": 1337,\n \"playerName\": \"Sean Plott\",\n \"cheatMode\": false,\n \"updatedAt\": \"2016-03-11T23:51:48.050Z\",\n \"createdAt\": \"2016-03-11T23:51:48.050Z\"\n}\n```\n\nKeeping tracks of individual object ids is not ideal, however. In most cases you will want to run a query over the collection, like so:\n\n```bash\n$ curl -X GET \\\n -H \"X-Parse-Application-Id: APPLICATION_ID\" \\\n http://localhost:1337/parse/classes/GameScore\n```\n```json\n// The response will provide all the matching objects within the `results` array:\n{\n \"results\": [\n {\n \"objectId\": \"2ntvSpRGIK\",\n \"score\": 1337,\n \"playerName\": \"Sean Plott\",\n \"cheatMode\": false,\n \"updatedAt\": \"2016-03-11T23:51:48.050Z\",\n \"createdAt\": \"2016-03-11T23:51:48.050Z\"\n }\n ]\n}\n\n```\n\nTo learn more about using saving and querying objects on Parse Server, check out the [Parse documentation](http://docs.parseplatform.org).\n\n### Connect your app to Parse Server\n\nParse provides SDKs for all the major platforms. Refer to the Parse Server guide to [learn how to connect your app to Parse Server](https://docs.parseplatform.org/parse-server/guide/#using-parse-sdks-with-parse-server).\n\n## Running Parse Server elsewhere\n\nOnce you have a better understanding of how the project works, please refer to the [Parse Server wiki](https://github.com/parse-community/parse-server/wiki) for in-depth guides to deploy Parse Server to major infrastructure providers. Read on to learn more about additional ways of running Parse Server.\n\n### Parse Server Sample Application\n\nWe have provided a basic [Node.js application](https://github.com/parse-community/parse-server-example) that uses the Parse Server module on Express and can be easily deployed to various infrastructure providers:\n\n* [Heroku and mLab](https://devcenter.heroku.com/articles/deploying-a-parse-server-to-heroku)\n* [AWS and Elastic Beanstalk](http://mobile.awsblog.com/post/TxCD57GZLM2JR/How-to-set-up-Parse-Server-on-AWS-using-AWS-Elastic-Beanstalk)\n* [Google App Engine](https://medium.com/@justinbeckwith/deploying-parse-server-to-google-app-engine-6bc0b7451d50)\n* [Microsoft Azure](https://azure.microsoft.com/en-us/blog/azure-welcomes-parse-developers/)\n* [SashiDo](https://blog.sashido.io/tag/migration/)\n* [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-run-parse-server-on-ubuntu-14-04)\n* [Pivotal Web Services](https://github.com/cf-platform-eng/pws-parse-server)\n* [Back4app](http://blog.back4app.com/2016/03/01/quick-wizard-migration/)\n* [Glitch](https://glitch.com/edit/#!/parse-server)\n* [Flynn](https://flynn.io/blog/parse-apps-on-flynn)\n\n### Parse Server + Express\n\nYou can also create an instance of Parse Server, and mount it on a new or existing Express website:\n\n```js\nvar express = require('express');\nvar ParseServer = require('parse-server').ParseServer;\nvar app = express();\n\nvar api = new ParseServer({\n databaseURI: 'mongodb://localhost:27017/dev', // Connection string for your MongoDB database\n cloud: './cloud/main.js', // Path to your Cloud Code\n appId: 'myAppId',\n masterKey: 'myMasterKey', // Keep this key secret!\n fileKey: 'optionalFileKey',\n serverURL: 'http://localhost:1337/parse' // Don't forget to change to https if needed\n});\n\n// Serve the Parse API on the /parse URL prefix\napp.use('/parse', api);\n\napp.listen(1337, function() {\n console.log('parse-server-example running on port 1337.');\n});\n```\n\nFor a full list of available options, run `parse-server --help` or take a look at [Parse Server Configurations](http://parseplatform.org/parse-server/api/master/ParseServerOptions.html).\n\n## Configuration\n\nParse Server can be configured using the following options. You may pass these as parameters when running a standalone `parse-server`, or by loading a configuration file in JSON format using `parse-server path/to/configuration.json`. If you're using Parse Server on Express, you may also pass these to the `ParseServer` object as options.\n\nFor the full list of available options, run `parse-server --help` or take a look at [Parse Server Configurations](http://parseplatform.org/parse-server/api/master/ParseServerOptions.html).\n\n### Basic options\n\n* `appId` **(required)** - The application id to host with this server instance. You can use any arbitrary string. For migrated apps, this should match your hosted Parse app.\n* `masterKey` **(required)** - The master key to use for overriding ACL security. You can use any arbitrary string. Keep it secret! For migrated apps, this should match your hosted Parse app.\n* `databaseURI` **(required)** - The connection string for your database, i.e. `mongodb://user:pass@host.com/dbname`. Be sure to [URL encode your password](https://app.zencoder.com/docs/guides/getting-started/special-characters-in-usernames-and-passwords) if your password has special characters.\n* `port` - The default port is 1337, specify this parameter to use a different port.\n* `serverURL` - URL to your Parse Server (don't forget to specify http:// or https://). This URL will be used when making requests to Parse Server from Cloud Code.\n* `cloud` - The absolute path to your cloud code `main.js` file.\n* `push` - Configuration options for APNS and GCM push. See the [Push Notifications quick start](http://docs.parseplatform.org/parse-server/guide/#push-notifications_push-notifications-quick-start).\n\n### Client key options\n\nThe client keys used with Parse are no longer necessary with Parse Server. If you wish to still require them, perhaps to be able to refuse access to older clients, you can set the keys at initialization time. Setting any of these keys will require all requests to provide one of the configured keys.\n\n* `clientKey`\n* `javascriptKey`\n* `restAPIKey`\n* `dotNetKey`\n\n### Email verification and password reset\n\nVerifying user email addresses and enabling password reset via email requires an email adapter. As part of the `parse-server` package we provide an adapter for sending email through Mailgun. To use it, sign up for Mailgun, and add this to your initialization code:\n\n```js\nvar server = ParseServer({\n ...otherOptions,\n // Enable email verification\n verifyUserEmails: true,\n\n // if `verifyUserEmails` is `true` and\n // if `emailVerifyTokenValidityDuration` is `undefined` then\n // email verify token never expires\n // else\n // email verify token expires after `emailVerifyTokenValidityDuration`\n //\n // `emailVerifyTokenValidityDuration` defaults to `undefined`\n //\n // email verify token below expires in 2 hours (= 2 * 60 * 60 == 7200 seconds)\n emailVerifyTokenValidityDuration: 2 * 60 * 60, // in seconds (2 hours = 7200 seconds)\n\n // set preventLoginWithUnverifiedEmail to false to allow user to login without verifying their email\n // set preventLoginWithUnverifiedEmail to true to prevent user from login if their email is not verified\n preventLoginWithUnverifiedEmail: false, // defaults to false\n\n // The public URL of your app.\n // This will appear in the link that is used to verify email addresses and reset passwords.\n // Set the mount path as it is in serverURL\n publicServerURL: 'https://example.com/parse',\n // Your apps name. This will appear in the subject and body of the emails that are sent.\n appName: 'Parse App',\n // The email adapter\n emailAdapter: {\n module: '@parse/simple-mailgun-adapter',\n options: {\n // The address that your emails come from\n fromAddress: 'parse@example.com',\n // Your domain from mailgun.com\n domain: 'example.com',\n // Your API key from mailgun.com\n apiKey: 'key-mykey',\n }\n },\n\n // account lockout policy setting (OPTIONAL) - defaults to undefined\n // if the account lockout policy is set and there are more than `threshold` number of failed login attempts then the `login` api call returns error code `Parse.Error.OBJECT_NOT_FOUND` with error message `Your account is locked due to multiple failed login attempts. Please try again after minute(s)`. After `duration` minutes of no login attempts, the application will allow the user to try login again.\n accountLockout: {\n duration: 5, // duration policy setting determines the number of minutes that a locked-out account remains locked out before automatically becoming unlocked. Set it to a value greater than 0 and less than 100000.\n threshold: 3, // threshold policy setting determines the number of failed sign-in attempts that will cause a user account to be locked. Set it to an integer value greater than 0 and less than 1000.\n },\n // optional settings to enforce password policies\n passwordPolicy: {\n // Two optional settings to enforce strong passwords. Either one or both can be specified.\n // If both are specified, both checks must pass to accept the password\n // 1. a RegExp object or a regex string representing the pattern to enforce\n validatorPattern: /^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.{8,})/, // enforce password with at least 8 char with at least 1 lower case, 1 upper case and 1 digit\n // 2. a callback function to be invoked to validate the password\n validatorCallback: (password) => { return validatePassword(password) },\n validationError: 'Password must contain at least 1 digit.' // optional error message to be sent instead of the default \"Password does not meet the Password Policy requirements.\" message.\n doNotAllowUsername: true, // optional setting to disallow username in passwords\n maxPasswordAge: 90, // optional setting in days for password expiry. Login fails if user does not reset the password within this period after signup/last reset.\n maxPasswordHistory: 5, // optional setting to prevent reuse of previous n passwords. Maximum value that can be specified is 20. Not specifying it or specifying 0 will not enforce history.\n //optional setting to set a validity duration for password reset links (in seconds)\n resetTokenValidityDuration: 24*60*60, // expire after 24 hours\n }\n});\n```\n\nYou can also use other email adapters contributed by the community such as:\n- [parse-smtp-template (Multi Language and Multi Template)](https://www.npmjs.com/package/parse-smtp-template)\n- [parse-server-postmark-adapter](https://www.npmjs.com/package/parse-server-postmark-adapter)\n- [parse-server-sendgrid-adapter](https://www.npmjs.com/package/parse-server-sendgrid-adapter)\n- [parse-server-mandrill-adapter](https://www.npmjs.com/package/parse-server-mandrill-adapter)\n- [parse-server-simple-ses-adapter](https://www.npmjs.com/package/parse-server-simple-ses-adapter)\n- [parse-server-mailgun-adapter-template](https://www.npmjs.com/package/parse-server-mailgun-adapter-template)\n- [parse-server-sendinblue-adapter](https://www.npmjs.com/package/parse-server-sendinblue-adapter)\n- [parse-server-mailjet-adapter](https://www.npmjs.com/package/parse-server-mailjet-adapter)\n- [simple-parse-smtp-adapter](https://www.npmjs.com/package/simple-parse-smtp-adapter)\n- [parse-server-generic-email-adapter](https://www.npmjs.com/package/parse-server-generic-email-adapter)\n\n### Custom Pages\n\nIt’s possible to change the default pages of the app and redirect the user to another path or domain.\n\n```js\nvar server = ParseServer({\n ...otherOptions,\n\n customPages: {\n passwordResetSuccess: \"http://yourapp.com/passwordResetSuccess\",\n verifyEmailSuccess: \"http://yourapp.com/verifyEmailSuccess\",\n parseFrameURL: \"http://yourapp.com/parseFrameURL\",\n linkSendSuccess: \"http://yourapp.com/linkSendSuccess\",\n linkSendFail: \"http://yourapp.com/linkSendFail\",\n invalidLink: \"http://yourapp.com/invalidLink\",\n invalidVerificationLink: \"http://yourapp.com/invalidVerificationLink\",\n choosePassword: \"http://yourapp.com/choosePassword\"\n }\n})\n```\n\n### Using environment variables to configure Parse Server\n\nYou may configure the Parse Server using environment variables:\n\n```bash\nPORT\nPARSE_SERVER_APPLICATION_ID\nPARSE_SERVER_MASTER_KEY\nPARSE_SERVER_DATABASE_URI\nPARSE_SERVER_URL\nPARSE_SERVER_CLOUD\n```\n\nThe default port is 1337, to use a different port set the PORT environment variable:\n\n```bash\n$ PORT=8080 parse-server --appId APPLICATION_ID --masterKey MASTER_KEY\n```\n\nFor the full list of configurable environment variables, run `parse-server --help` or take a look at [Parse Server Configuration](https://github.com/parse-community/parse-server/blob/master/src/Options/Definitions.js).\n\n### Available Adapters\n\nAll official adapters are distributed as scoped pacakges on [npm (@parse)](https://www.npmjs.com/search?q=scope%3Aparse).\n\nSome well maintained adapters are also available on the [Parse Server Modules](https://github.com/parse-server-modules) organization.\n\nYou can also find more adapters maintained by the community by searching on [npm](https://www.npmjs.com/search?q=parse-server%20adapter&page=1&ranking=optimal).\n\n### Configuring File Adapters\n\nParse Server allows developers to choose from several options when hosting files:\n\n* `GridFSBucketAdapter`, which is backed by MongoDB;\n* `S3Adapter`, which is backed by [Amazon S3](https://aws.amazon.com/s3/); or\n* `GCSAdapter`, which is backed by [Google Cloud Storage](https://cloud.google.com/storage/)\n\n`GridFSBucketAdapter` is used by default and requires no setup, but if you're interested in using S3 or Google Cloud Storage, additional configuration information is available in the [Parse Server guide](http://docs.parseplatform.org/parse-server/guide/#configuring-file-adapters).\n\n### Idempodency Enforcement\n \n**Caution, this is an experimental feature that may not be appropriate for production.**\n\nThis feature deduplicates identical requests that are received by Parse Server mutliple times, typically due to network issues or network adapter access restrictions on mobile operating systems.\n\nIdentical requests are identified by their request header `X-Parse-Request-Id`. Therefore a client request has to include this header for deduplication to be applied. Requests that do not contain this header cannot be deduplicated and are processed normally by Parse Server. This means rolling out this feature to clients is seamless as Parse Server still processes request without this header when this feature is enbabled.\n\n> This feature needs to be enabled on the client side to send the header and on the server to process the header. Refer to the specific Parse SDK docs to see whether the feature is supported yet.\n\nDeduplication is only done for object creation and update (`POST` and `PUT` requests). Deduplication is not done for object finding and deletion (`GET` and `DELETE` requests), as these operations are already idempotent by definition.\n\n#### Configuration example\n```\nlet api = new ParseServer({\n idempotencyOptions: {\n paths: [\".*\"], // enforce for all requests\n ttl: 120 // keep request IDs for 120s\n }\n}\n```\n#### Parameters\n\n| Parameter | Optional | Type | Default value | Example values | Environment variable | Description |\n|-----------|----------|--------|---------------|-----------|-----------|-------------|\n| `idempotencyOptions` | yes | `Object` | `undefined` | | PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_OPTIONS | Setting this enables idempotency enforcement for the specified paths. |\n| `idempotencyOptions.paths`| yes | `Array` | `[]` | `.*` (all paths, includes the examples below),
`functions/.*` (all functions),
`jobs/.*` (all jobs),
`classes/.*` (all classes),
`functions/.*` (all functions),
`users` (user creation / update),
`installations` (installation creation / update) | PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_PATHS | An array of path patterns that have to match the request path for request deduplication to be enabled. The mount path must not be included, for example to match the request path `/parse/functions/myFunction` specifiy the path pattern `functions/myFunction`. A trailing slash of the request path is ignored, for example the path pattern `functions/myFunction` matches both `/parse/functions/myFunction` and `/parse/functions/myFunction/`. |\n| `idempotencyOptions.ttl` | yes | `Integer` | `300` | `60` (60 seconds) | PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_TTL | The duration in seconds after which a request record is discarded from the database. Duplicate requests due to network issues can be expected to arrive within milliseconds up to several seconds. This value must be greater than `0`. |\n\n#### Notes\n\n- This feature is currently only available for MongoDB and not for Postgres.\n\n### Logging\n\nParse Server will, by default, log:\n* to the console\n* daily rotating files as new line delimited JSON\n\nLogs are also viewable in Parse Dashboard.\n\n**Want to log each request and response?** Set the `VERBOSE` environment variable when starting `parse-server`. Usage :- `VERBOSE='1' parse-server --appId APPLICATION_ID --masterKey MASTER_KEY`\n\n**Want logs to be in placed in a different folder?** Pass the `PARSE_SERVER_LOGS_FOLDER` environment variable when starting `parse-server`. Usage :- `PARSE_SERVER_LOGS_FOLDER='' parse-server --appId APPLICATION_ID --masterKey MASTER_KEY`\n\n**Want to log specific levels?** Pass the `logLevel` parameter when starting `parse-server`. Usage :- `parse-server --appId APPLICATION_ID --masterKey MASTER_KEY --logLevel LOG_LEVEL`\n\n**Want new line delimited JSON error logs (for consumption by CloudWatch, Google Cloud Logging, etc)?** Pass the `JSON_LOGS` environment variable when starting `parse-server`. Usage :- `JSON_LOGS='1' parse-server --appId APPLICATION_ID --masterKey MASTER_KEY`\n\n# Live Queries\n\nLive queries are meant to be used ","has_starred","hub_user","immutable_tags_settings",{"_70":11,"_71":72},"enabled","rules",[73],".*","is_automated","permissions",{"_77":17,"_78":11,"_79":11},"read","write","admin","user","storage_size",164049489,"orgData","recentTags",[86,123],{"_87":39,"_88":89,"_90":91,"_92":93,"_94":95,"_45":112,"_113":89,"_114":28,"_115":51,"_52":116,"_117":118,"_119":103,"_120":112,"_121":61,"_122":17},"content_type","creator",12238393,"full_size",97064981,"id",145738916,"images",[96],{"_97":98,"_99":100,"_101":43,"_102":103,"_104":105,"_106":107,"_108":43,"_109":-5,"_110":91,"_58":61,"_111":-5},"architecture","amd64","digest","sha256:3cf257af497b66501bb93febe82e87ba48ce126e7f3c07bd8dad8f3efd481555","features","last_pulled","2026-09-12T15:31:07.37563136Z","last_pushed","2021-04-15T14:53:35Z","os","linux","os_features","os_version","size","variant","2021-04-15T14:53:34.38926Z","last_updater","last_updater_username","media_type","latest","repository",12324372,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_87":39,"_88":89,"_90":124,"_92":125,"_94":126,"_45":131,"_113":89,"_114":28,"_115":51,"_52":132,"_117":118,"_119":129,"_120":131,"_121":61,"_122":17},107780346,145739250,[127],{"_97":98,"_99":128,"_101":43,"_102":129,"_104":130,"_106":107,"_108":43,"_109":-5,"_110":124,"_58":61,"_111":-5},"sha256:55fe7cac347a344bf77befd61b5a7a08c5267cc476ffe67370bad1b47b9dc1a9","2026-09-14T08:27:19.491176603Z","2021-04-15T14:55:17Z","2021-04-15T14:55:16.788798Z","4.5.0-patch1","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":142,"_149":150,"_138":163,"_164":11},{"_35":143,"_37":144,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":145,"_52":30,"_27":28,"_53":54,"_55":39,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":146,"_74":11,"_75":148,"_80":28,"_81":82},[],[39],[51],{"_70":11,"_71":147},[73],{"_77":17,"_78":11,"_79":11},"tags",{"_151":152,"_153":-5,"_154":-5,"_155":156},"count",2,"next","previous","results",[157,160],{"_87":39,"_88":89,"_90":124,"_92":125,"_94":158,"_45":131,"_113":89,"_114":28,"_115":51,"_52":132,"_117":118,"_119":129,"_120":131,"_121":61,"_122":17},[159],{"_97":98,"_99":128,"_101":43,"_102":129,"_104":130,"_106":107,"_108":43,"_109":-5,"_110":124,"_58":61,"_111":-5},{"_87":39,"_88":89,"_90":91,"_92":93,"_94":161,"_45":112,"_113":89,"_114":28,"_115":51,"_52":116,"_117":118,"_119":103,"_120":112,"_121":61,"_122":17},[162],{"_97":98,"_99":100,"_101":43,"_102":103,"_104":105,"_106":107,"_108":43,"_109":-5,"_110":91,"_58":61,"_111":-5},[],"canDeleteTags","actionData","errors"]

fischerscode/parse-server

Tags for fischerscode/parse-server