Provide a way to store mysql_user and mysql_password in one place about homer-api HOT 11 CLOSED

please make modification and a merge request. We will accept it ASAP.
the ideally will be create a config file i.e. /etc/homer/rotate.conf and read this information from there.

from homer-api.

Okay, but in the past, the configuration files were like preferences_example.php, and now they are moved to preferences.php. This makes it impossible for those files to be excluded in a .gitignore.
According to the commit message, this was done for some packaging changes.

from homer-api.

@michaelarnauts just thinking out loud here, if the only changes are configuration files wouldn't simply stashing and restoring after a pull should do the trick? git stash && git pull && git stash pop

This being said a .gitignore config file as Alexandr suggest could do the trick and provide details for all scripts/files requiring them with some work or via an update script.

from homer-api.

@lmangani true, but that tend to give conflicts when changes in those files are also made.

The cleanest way is to have a configuration.php.example file, and upon installation, copy that to a configuration.php file, what is ignored trough a .gitignore. At least, that's how most projects do it. I just don't know how that relates to the packaging changes that are being made the in the last weeks/months.

from homer-api.

We will quickly discuss the package implications and how to implement this best

from homer-api.

@michaelarnauts implemented, the filenames are restored to their correct names now as they were - thanks for raising this and please confirm back to close the issue

from homer-api.

@lmangani you need to remove the configuration.php and preferences.php, and add those to .gitignore. Otherwise, they are still marked as changed on a git pull.

This also doesn't resolve this issue, since all scripts still need to be changed. This issue is to have one place where the configuration is stored.

from homer-api.

sorry, but we did it. Please check homer-api git

from homer-api.

@adubovikov sorry, I only checked the latest commit :)

I think we still need a way to have one configuration file that is easy parsable with PHP and Perl.

from homer-api.

the configurations for php and for rotation scripts should be separated,
because you can have multiple DBs, but only one web UI.

so, the idea to create one config for rotation scripts is not bad, but only
for rotations scritps.

On 7 January 2016 at 15:26, Michaël Arnauts [email protected]
wrote:

@adubovikov https://github.com/adubovikov sorry, I only checked the
latest commit :)

I think we still need a way to have one configuration file that is easy
parsable with PHP and Perl.

—
Reply to this email directly or view it on GitHub
#66 (comment)
.

from homer-api.

testers are welcome

https://github.com/sipcapture/homer-api/tree/master/scripts/new

from homer-api.