billions-minister-2901
02/23/2024, 3:26 PMchilly-king-10285
02/23/2024, 3:26 PMchilly-king-10285
02/23/2024, 3:27 PM--dev
flag from kratos serve
when preparing for production ([source](https://www.ory.sh/docs/kratos/guides/production)). 3. API Gateway: It's recommended to run Ory Keto and Ory Kratos behind an API gateway or a load balancer for security reasons. The Admin API should not be exposed to the public internet unsecured ([source](https://www.ory.sh/docs/keto/guides/production), [source](https://www.ory.sh/docs/kratos/guides/production)). 4. Scaling: There are no additional requirements for scaling when self-hosting Ory Keto or Ory Kratos, just spin up another container ([source](https://www.ory.sh/docs/keto/guides/production), [source](https://www.ory.sh/docs/kratos/guides/production)). 5. Ory CLI: The Ory CLI provides a convenient way to configure and manage projects. It also contains Ory Proxy - a reverse proxy that rewrites cookies to match the domain your application is currently on. This is necessary to avoid issues with the browser CORS policy ([source](https://www.ory.sh/docs/getting-started/integrate-auth/go#install-ory-cli)). 6. Ory Proxy: You can use Ory Proxy in a production setup when self-hosting Ory components. Set the entry point URL to the domain where you want to expose the app through the Ory Proxy ([source](https://www.ory.sh/docs/guides/cli/proxy-and-tunnel#use-ory-proxy-when-self-hosting)). As for your specific question about downloading your entire config, making changes, and then reapplying using the Ory CLI, the provided extracts do not contain specific information on this process. However, it's generally a good practice to review and adjust your configuration settings when moving from a development to a production environment. For more detailed instructions, you may want to refer to the official Ory documentation or seek advice from the Ory community.billions-minister-2901
02/23/2024, 3:31 PMchilly-king-10285
02/23/2024, 3:31 PMchilly-king-10285
02/23/2024, 3:32 PM