#Convex Self-Hosted Logs

1 messages · Page 1 of 1 (latest)

lilac knollBOT
#

Hi @wraith lintel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

I'm sorry, but the knowledge sources do not contain explicit information about how to turn off or adjust the INFO logs specifically for convex-cloud-http in a self-hosted Convex deployment. The available documentation does mention that you can set log levels for certain components (like the Action Retrier via the ACTION_RETRIER_LOG_LEVEL environment variable), but there is no mention of a general log level configuration or a way to disable INFO logs globally or specifically for convex-cloud-http in self-hosted setups.

If you need more granular control over logging, you may want to check the Convex GitHub repository or ask in the #self-hosted channel of the Convex Discord community for more detailed support, as suggested in the self-hosting documentation Self Hosting.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@wraith lintel Kapa.ai is still learning and improving, please let me know how I did by reacting below.

wraith lintel
#

@lilac knoll if I have a postgres db backing my convex installation, what do I need to do to perform automatic backups of my self hosted installation?

lilac knollBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

The knowledge sources do not provide explicit instructions for setting up automatic backups of a self-hosted Convex installation when using a Postgres database as the backend. The available documentation covers how to connect Convex to Postgres and how to export/import data using Convex CLI tools (such as npx convex export), but it does not detail an automated backup process for the underlying Postgres database in a self-hosted context.

For self-hosted setups, you are responsible for managing your own database backups. This typically means you should use standard Postgres backup tools (like pg_dump, pg_basebackup, or managed service features) to schedule and store backups of your Postgres database. The Convex documentation does recommend replicating your database and saving snapshots for failure recovery, but does not provide a built-in mechanism for automating these backups within Convex itself. You will need to set up and manage this process according to your operational requirements and the capabilities of your hosting provider or Postgres setup Self-Hosting with Convex: Everything You Need to Know.

If you need more detailed, Convex-specific guidance, it is recommended to ask in the #self-hosted channel of the Convex Discord community, as suggested in the self-hosting documentation Self Hosting.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: