Setting this to '*' means that BMO will trust the X-Forwarded-For header. This can be '*' if only the load balancer can connect to this container. BMO_inbound_proxies This is a list of IP addresses that we expect proxies to come from. High level of entropy, as it probably won't change for a very long time. Jwts, so all oauth clients will need to start over. It's very important that this key is kept secret and it should beĭifferent from the side_wide_secret. BMO_jwt_secret This secret key is used by your installation for the creation and validation It's very important that this key is kept secret.
Security features in Bugzilla, to protect against certain types of attacks. BMO_site_wide_secret This secret key is used by your installation for the creation and BMO_db_pass The password for the user above. BMO_db_user The database user to connect as. BMO_db_host The DNS name or IP address of the host that the database server runs on. Supported database and the name of the module (before ".pm") corresponds to a Obtained by listing Bugzilla/DB directory - every module corresponds to one
Names (such as ) must point to this same Bugzilla Remember, though, that all those possible domain This will limit attachments to accessing only otherĪttachments on the same bug. Replaced with the ID of the current bug that the attachment is on, when youĪccess an attachment. That is, a different domain name that resolves to thisįor added security, you can insert %bugid% into the URL, which will be Parameter to an alternate URL for your Bugzilla that is not the same as If you would like additional security on attachments to avoid this, set this Malicious attachment to steal your cookies or perform an attack on Bugzilla When the allow_attachment_display parameter is on, it is possible for a BMO_canonical_urlbase The public URL for the production instance, if different from urlbase above. Note that if this begins with and BMO_inbound_proxies is set to '*' Bugzilla will believe the connection to it BMO_urlbase The public URL for this instance.
This value and increase "MOJO_WORKERS" instead for better performance.ĭefault: 200 BUGZILLA_ALLOW_INSECURE_HTTP This should never be set in production. Non-blocking operations, to optimize for blocking operations you can decrease That high concurrency works best with applications that perform mostly Handle concurrently, before stopping to accept new incoming connections. Shutting down gracefully, drastically reducing the performance cost ofĭefault: 1 MOJO_CLIENTS Maximum number of accepted connections each worker process is allowed to This allows for new workers to be started while old ones are still Note that during zeroĭowntime software upgrades there will be twice as many workers active for aĭefault: 1 MOJO_SPARE Temporarily spawn up to this number of additional workers if there is a A good rule of thumb is two worker processes perĬPU core for applications that perform mostly non-blocking operations,īlocking operations often require more and benefit from decreasingĬoncurrency with "MOJO_CLIENTS" (often as low as 1). The httpd will listen on this port for incomingĭefault: 8000 MOJO_REVERSE_PROXY This tells the backend that it is behind a proxy.ĭefault: 1 MOJO_HEARTBEAT_INTERVAL How often (in seconds) will the manager process send a heartbeat to the workers.ĭefault: 10 MOJO_HEARTBEAT_TIMEOUT Maximum amount of time in seconds before a worker without a heartbeat will be stopped gracefullyĭefault: 120 MOJO_INACTIVITY_TIMEOUT Maximum amount of time in seconds a connection can be inactive before getting closed.ĭefault: 120 MOJO_WORKERS Number of worker processes. Environmental Variables PORT This must be a value >= 1024. httpd This will start apache listening for connections on $PORT shell This will start an interactive shell in the container. Container ArgumentsĬurrently, the entry point takes a single command argument. This repository is also a runnable docker container. This message shows that your installation appears to be working correctly.
0 kommentar(er)
