Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add README note about running on separate server, #191 #192

Merged
merged 3 commits into from
Jul 31, 2023
Merged

add README note about running on separate server, #191 #192

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ba66c91
add README note about running on separate server, #191
ThrawnCA Jul 31, 2023
0cf07bc
[QOLDEV-424] fix tests to avoid hardcoding resource IDs
ThrawnCA Jul 28, 2023
453d6f7
[QOLDEV-424] ensure consistent column name ordering in tests
ThrawnCA Jul 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,16 @@ can access the CKAN config, db and logging directly and avoids many HTTP calls.
This simplification makes sense because the xloader job doesn't need to do much
processing - mainly it is streaming the CSV file from disk into PostgreSQL.

It is still entirely possible to run the XLoader worker on a separate server,
if that is desired. The worker needs the following:

- A copy of CKAN installed in the same Python virtualenv (but not running).
- A copy of the CKAN config file.
- Access to the Redis instance that the running CKAN app uses to store jobs.
- Access to the database.

You can then run it via `ckan jobs worker` as below.

Caveat - column types
---------------------

Expand Down
Loading