Kohadevbox for testing Packages+Plack
Hi everyone, I hope you had a great weekend :-D We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily. To try/use it, you need to: (1) Install the latest vagrant: https://www.vagrantup.com/downloads.html (2) Install the latest ansible: http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-... (3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server (4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git (5) Checkout the 'ansible' branch. (6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc) (7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone (8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081 After this, you can enable Plack from within the VM by running: $ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!). So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release. Thanks in advance! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
Dear Tomas, Do you have koha docker (https://www.docker.com/) project ? kohadevbox image is too big. BR, longshan Tomas Cohen Arazi <tomascohen@gmail.com> 於 2015/9/21 (週一) 10:23 PM 寫道﹕ Hi everyone, I hope you had a great weekend :-D We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily. To try/use it, you need to: (1) Install the latest vagrant: https://www.vagrantup.com/downloads.html (2) Install the latest ansible: http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-... (3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server (4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git (5) Checkout the 'ansible' branch. (6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc) (7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone (8) Launch kohadevbox for the desired distribution: $ vagrant up trustyor $ vagrant up wheezyor $ vagrant up jessie Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080- Staff: http://localhost:8081 After this, you can enable Plack from within the VM by running: $ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!). So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release. Thanks in advance! -- Tomás Cohen AraziTheke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2. Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file? The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone) 2/ Can we imagine several instances running? How can we access them separately? 3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)? Cheers, Jonathan 2015-09-21 15:22 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I hope you had a great weekend :-D
We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily.
To try/use it, you need to:
(1) Install the latest vagrant: https://www.vagrantup.com/downloads.html
(2) Install the latest ansible:
http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-...
(3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server
(4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git
(5) Checkout the 'ansible' branch.
(6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc)
(7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone
(8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie
Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081
After this, you can enable Plack from within the VM by running:
$ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart
Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!).
So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release.
Thanks in advance!
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[TODO LATER] It would be great to fill ~/.my.cnf with [client] user=$db_user password=$db_pwd host=$db_host [mysql] default-character-set=utf8 2015-09-23 10:57 GMT+01:00 Jonathan Druart <jonathan.druart@bugs.koha-community.org>:
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2.
Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file? The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
2/ Can we imagine several instances running? How can we access them separately?
3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)?
Cheers, Jonathan
2015-09-21 15:22 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I hope you had a great weekend :-D
We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily.
To try/use it, you need to:
(1) Install the latest vagrant: https://www.vagrantup.com/downloads.html
(2) Install the latest ansible:
http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-...
(3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server
(4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git
(5) Checkout the 'ansible' branch.
(6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc)
(7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone
(8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie
Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081
After this, you can enable Plack from within the VM by running:
$ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart
Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!).
So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release.
Thanks in advance!
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Forget that, this is not needed. We have koha-mysql 2015-09-23 11:01 GMT+01:00 Jonathan Druart <jonathan.druart@bugs.koha-community.org>:
[TODO LATER] It would be great to fill ~/.my.cnf with [client] user=$db_user password=$db_pwd host=$db_host
[mysql] default-character-set=utf8
2015-09-23 10:57 GMT+01:00 Jonathan Druart <jonathan.druart@bugs.koha-community.org>:
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2.
Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file? The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
2/ Can we imagine several instances running? How can we access them separately?
3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)?
Cheers, Jonathan
2015-09-21 15:22 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I hope you had a great weekend :-D
We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily.
To try/use it, you need to:
(1) Install the latest vagrant: https://www.vagrantup.com/downloads.html
(2) Install the latest ansible:
http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-...
(3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server
(4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git
(5) Checkout the 'ansible' branch.
(6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc)
(7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone
(8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie
Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081
After this, you can enable Plack from within the VM by running:
$ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart
Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!).
So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release.
Thanks in advance!
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
2015-09-23 6:57 GMT-03:00 Jonathan Druart < jonathan.druart@bugs.koha-community.org>:
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2.
Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file?
That's because it is used by vagrant, to mount your local Koha clone as an NFS filesystem (we could use Virtualbox's folder sharing driver, but it is painfully slow). We should extend this to more options (LXC containers?).
The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
Yeah, that's on my TODO. Basically, we need to use that env var to control wether to clone from the ansible script or not. Currently, it is assumed that the clone exists.
2/ Can we imagine several instances running? How can we access them separately?
We should try. The main issue with the current Vagrantfile would be the fixed IP (needed for the NFS thing only). Maybe we could just define a different one for each vm definition (jessie, wheezy, etc). The port mapping should be handled that way too, to avoid collision.
3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)?
Magnus' branch currently lets you specify an SQL file to be loaded. That's on the TODO list too, the same for another feature Magnus implemented: controlling wether to load the shipped default data, or let the user go through the webinstaller.
Cheers, Jonathan
Thanks for the feedback. I'm sending a pull request to Chris Hall for koha-gitify to take care of the new plack.psgi file paths.
Hi everyone, I hope you had a great weekend :-D
We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full
2015-09-21 15:22 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>: packages
environment, suitable for testing Plack on packages. I already use it for my RM duties, daily.
To try/use it, you need to:
(1) Install the latest vagrant: https://www.vagrantup.com/downloads.html
(2) Install the latest ansible:
http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-...
(3) Install nfs-kernel-server (for re-using your host machine cloned
repo)
$ sudo apt-get install nfs-kernel-server
(4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git
(5) Checkout the 'ansible' branch.
(6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc)
(7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone
(8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie
Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081
After this, you can enable Plack from within the VM by running:
$ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart
Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!).
So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release.
Thanks in advance!
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
2015-09-23 6:57 GMT-03:00 Jonathan Druart < jonathan.druart@bugs.koha-community.org>:
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2.
Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file? The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
I've just fixed it so it clones the community repo (whatever you configure in user.yml actually) if the environment variable is not defined.
2/ Can we imagine several instances running? How can we access them separately?
It is not that easy, because we are mapping the ports at Vagrantfile-level. A combination of (host machine) /etc/hosts tweaks and apache vhosts tweaks (vagrant machine) might do it.
3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)?
That'd be great too. Right now I've just prepared the field for skip_webinstaller. Next could be that. Any help is welcome too ;-) -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
Thanks Tomas - I have started to test this and play around with it. Are others finding the time to do that as well? Great stuff here and really important for all of us. Please share your thoughts and comments with us all. We are getting closer to 3.22 and it looks like we're going to finally be fast - this plack work is awesome and so important! (plus we also need lots of help with Elastic Search, Browse, and RESTful apis - we need to get that functionality into Koha). Please now is the time to test, share comments, and let's do this - we can do it!!! Cheers, Brendan On Fri, Sep 25, 2015 at 2:53 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
2015-09-23 6:57 GMT-03:00 Jonathan Druart < jonathan.druart@bugs.koha-community.org>:
It works perfectly with a Jessie host. Note that I am using vagrant 1.6.5 and ansible 1.7.2.
Some questions: 1/ > $ export SYNC_REPO=/home/katrina/kohaclone Why this variable is not in the vars/user.yml file? The process explodes if not defined: TASK: [kohadevbox | Gitify the Koha instance] ********************************* failed: [jessie] => {"changed": true, "cmd": "./koha-gitify kohadev /home/vagrant/kohaclone", "delta": "0:00:00.045243", "end": "2015-09-23 09:12:58.035161", "rc": 2, "start": "2015-09-23 09:12:57.989918"} stderr: ERROR: git checkout not found at (/home/vagrant/kohaclone)
I've just fixed it so it clones the community repo (whatever you configure in user.yml actually) if the environment variable is not defined.
2/ Can we imagine several instances running? How can we access them separately?
It is not that easy, because we are mapping the ports at Vagrantfile-level. A combination of (host machine) /etc/hosts tweaks and apache vhosts tweaks (vagrant machine) might do it.
3/ Can we imagine a way to automatically insert a specific DB (from the contrib/sandboxes repo for instance)?
That'd be great too. Right now I've just prepared the field for skip_webinstaller. Next could be that. Any help is welcome too ;-)
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info@bywatersolutions.com
Just realized that vars/user.yml is not used (default values are). It certainly comes from site.yml which has: 9 - vars/defaults.yml 10 # - vars/user.yml 2015-09-21 15:22 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I hope you had a great weekend :-D
We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily.
To try/use it, you need to:
(1) Install the latest vagrant: https://www.vagrantup.com/downloads.html
(2) Install the latest ansible:
http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-...
(3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server
(4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git
(5) Checkout the 'ansible' branch.
(6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc)
(7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone
(8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie
Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081
After this, you can enable Plack from within the VM by running:
$ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart
Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!).
So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release.
Thanks in advance!
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
2015-09-23 7:58 GMT-03:00 Jonathan Druart < jonathan.druart@bugs.koha-community.org>:
Just realized that vars/user.yml is not used (default values are). It certainly comes from site.yml which has: 9 - vars/defaults.yml 10 # - vars/user.yml
Thanks, I've just fixed it. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
participants (4)
-
Brendan Gallagher -
Jonathan Druart -
long_sam.tw -
Tomas Cohen Arazi