Project

General

Custom queries

Profile

Actions

Bug #15175

closed

Can't handle relative paths to sqlite databases

Added by Christopher Huhn about 9 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Hi,

I installed foreman and foreman-sqlite3 from the Debian packages.
The default database.yml contains relative path to db/production.sqlite3.

This is not properly handled by the tasks plugin: It tries to create
/db/dynflow-production.sqlite3 instead of /usr/share/foreman/db/dynflow-production.sqlite3. This fails.

Giving the absolute path in database.yml fixes the issue. Anyhow the plugin should handle relative paths correctly esp. if that's the documented default setup recommendation.

Kind regards,
Christopher

Actions #1

Updated by Tomer Brisker over 5 years ago

SQlite support in production will be removed in Foreman 2.0. Please migrate to postgresql.

Actions #2

Updated by Tomer Brisker over 5 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF