Hey Indranil,

 

I’m not sure if kohadevbox is getting much love and attention, especially on 
Windows, anymore. 

 

Happy to be corrected if I’m wrong but I think many people are moving / have 
moved to koha-testing-docker: 
https://gitlab.com/koha-community/koha-testing-docker. 

 

The documentation could use a bit of work but you can update the KOHA_IMAGE 
variable to pick different images available from 
https://hub.docker.com/r/koha/koha-testing/tags (I actually just noticed that 
this moment). My guess is “master” is for stretch since there are master-jessie 
and master-buster available as well. 

 

Personally, I use Docker Desktop on Windows, and I find mounting a volume with 
my Git can be painful, so I actually just created a named volume (within the 
Docker Desktop VM) and keep my Git clone there. That way it’s just all Linux 
all the time. 

 

Alas, I deleted my last kohadevbox recently, so can’t help you on that one, I’m 
afraid. 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of 
Indranil Das Gupta
Sent: Sunday, 2 February 2020 7:07 PM
To: Koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof

 

Hi all,

 

I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after 
stretch64 

 

Things I've done so far:

1. I had to switch the distribution to 
https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise 
I was hitting the missing linux-headers for vbox guest additions.

 

2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 
SYNC_REPO="/home/vagrant/kohaclone" vagrant up

 

3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via 
putty

 

4. But no cheese when i try to access http://localhost:8081 either inside the 
VM or from my host box

 

5. the .deb installation did go through, because there is /usr/share/koha and 
the koha-* commands are accessible e.g. koha-list. koha-passwd so package got 
installed.

 

6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems 
because the installation has gotten gitified and there is nothing there at the 
moment.

 

7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git 
kohaclone` in /home/vagrant to see if that makes a difference.

 

My question: kohadevbox README.md says - "A clone of the official Koha Git 
repo, or a NFS-mounted git repository from your host machine." 

 

So what am I missing here? Cluesticks / brickbats welcome... and expected :-)

thanks

 

-- 
Indranil Das Gupta
L2C2 Technologies

Phone : +91-98300-20971

WWW : http://www.l2c2.co.in
Blog    : http://blog.l2c2.co.in
IRC     : indradg on irc://irc.freenode.net <http://irc.freenode.net> 
Twitter : indradg

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://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/

Reply via email to