[#644] forge_get_config doesn't need to connect to the database

Description

Summary:

Detailed description

forgegetconfig config_path

FusionForge Could Not Connect to Database:

This may cause issues when e.g. the database is not running or not installed yet (packaging bootstrap). This also makes multiple calls to forgegetconfig (in scripts) quite slow because they initiate a DB connection everytime.

There's a workaround with:

FUSIONFORGENOPLUGINS=true forgegetconfig config_path

/etc/gforge

FUSIONFORGENOPLUGINS=true forgegetconfig plugin_status hudson

valid

but as you can see this doesn't make sense (the plugins are not disabled, and we don't want to disable the plugins, just not load the DB unless necessary).

How do you think we should initiate database-free forgegetconfig ?

General Information
Submitted by:
Sylvain Beucler
Date Submitted: 2014-03-17 09:59
Last Modified by: Nobody
Last Modified: 2017-11-02 20:00
Date Closed: 2014-03-19 12:28
Permalink: https://fusionforge.org/tracker/a_follow.php/644
Actions
Internal Fields
Data Type: Bugs
Assigned to: Sylvain Beucler (beuc-inria)
State: Closed
Priority: 3
Extra Fields
Resolution:
Fixed
Severity:
none
Target Release:
5.3
Follow-up tabs
Message  ↓
Date: 2014-03-18 21:17
Sender: Beuc ^^

Introducing FUSIONFORGENODB with the currently same effect.

Date: 2014-03-17 13:26
Sender: Sylvain Beucler

Another situation where we want access to the config without the DB is when running non-privileged scripts (hooks, scripts run by www-data...).

No attached documents

No related commits.

Field Old Value Date By
Target ReleaseNone2014-05-12 16:55
Franck Villaume
assigned_tonone2014-03-20 10:25
Franck Villaume
status_idOpen2014-03-19 12:28
Sylvain Beucler
close_dateNone2014-03-19 12:28
Sylvain Beucler
ResolutionNone2014-03-19 12:28
Sylvain Beucler

No relations found.