CARTO can be installed on a local server, or set of servers, either directly or using our commercial installer.

Configuration: post-installation

Scheduled tasks

Some functionalities in CARTO require the running of certain tasks periodically (e.g. setting up a cron job). This section describes such tasks, their usage, and how to configure them.

To set up a cron job to be executed under a given user (e.g. carto), run the following command:

1
crontab -u carto -e

This will allow you to edit the crontab for that user using your default editor ($EDITOR), then all you need is just to paste the cron you want to run into that file (see below).

Sync tables

Sync tables is a feature within CARTO Builder that allows users to set up automatic table synchronization of datasets uploaded from external services. It is done as a background job in a Resque.

However, for this feature to work in an On-Premise installation, a rake task that checks for tables that need to be synced and enqueues them to be later processed by a Resque worker needs to be executed.

This rake task is meant to be run as a cron job (ideally every minute, running it less often may cause update lag).

1
*/1 * * * * /opt/carto/builder-tools/embedded/bin/carto-builder-exec-rake.sh cartodb:sync_tables
Note
`/opt/carto/builder-tools/embedded/bin` is the default installation path for builder tools. If that path was changed in the installation, modify accordingly.

OAuth tokens (CARTO_VERSION >= 3.0.1)

A rake task is required to periodically clean expired OAuth tokens. A reasonable schedule would be to run it every minute.

1
*/1 * * * * /opt/carto/builder-tools/embedded/bin/carto-builder-exec-rake.sh cartodb:oauth:destroy_expired_oauth_keys
Note
`/opt/carto/builder-tools/embedded/bin` is the default installation path for builder tools. If that path was changed in the installation, modify accordingly.