A docker based parse server implementation
230
See above for all documentation.
Parse listens on the path given in SERVER_URL, if any, not /parse
as in the upstream examples, so it can be easily served from HAProxy and
composed with other services. For example with multiple apps and envs:
https://parse.example.com/appname/prod/
https://parse.example.com/appname/dev/
https://parse.example.com/anotherapp/prod/
Logs are written to STDOUT in "pretty" Bunyan format, and to file in "raw" JSON format. The welcome message is written to STDERR to not interfere.
APP_ID RequiredAPP_NAME Optional. Sets both the Parse internal app name, and in the logsCLIENT_KEY RequiredCLOUD Defaults to /cloud/main.jsDATABASE_URI Defaults to mongodb://mongo, so you can link to mongo easilyDOTNET_KEY Defaults to CLIENT_KEYJAVASCRIPT_KEY Defaults to CLIENT_KEYMASTER_KEY RequiredMAX_UPLOAD_SIZE Defaults to '100mb'PORT Defaults to 1337, coerced to a numberPUBLIC_SERVER_URL Public-facing URL for server, defaults to SERVER_URLREST_API_KEY Defaults to CLIENT_KEYSERVER_URL RequiredMAILGUN_DOMAIN Mailgun domainMAILGUN_FROM Mailgun From addressMAILGUN_KEY Mailgun API keyparse.log and rotated every day)Exposes 1337 by default.
Content type
Image
Digest
Size
267.8 MB
Last updated
over 9 years ago
docker pull reitfibel/parse-server