About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
installation:vagrant

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
installation:vagrant [2017/08/03 13:56] – [Setting Up the Virtual Machine] demiankatzinstallation:vagrant [2023/04/14 16:40] – Moved other options -- now too old to be useful. demiankatz
Line 9: Line 9:
 ==== Setting Up the Virtual Machine ==== ==== Setting Up the Virtual Machine ====
  
-To get started, make sure that [[http://www.vagrantup.com/|Vagrant]] is installed on your system, then simply go to the VuFind directory and run:+To get started, make sure that [[http://www.vagrantup.com/|Vagrant]] is installed on your system, then simply go to your VuFind directory (preferably a fresh, clean checkout from [[development:recommended_tools:git|Git]] with Composer dependencies already installed, if you're just getting started) and run:
  
   vagrant up   vagrant up
Line 35: Line 35:
 If you want to view Solr in a web browser on your host machine, it should be port-mapped to port 4568, so you can view the admin at <nowiki>http://localhost:4568/solr</nowiki>. If you want to view Solr in a web browser on your host machine, it should be port-mapped to port 4568, so you can view the admin at <nowiki>http://localhost:4568/solr</nowiki>.
  
 +== Notes for Windows Users ==
 +
 +:!: For Windows users, the ''solr.sh'' and ''import-marc.sh'' may fail to start with a "bad interpreter" error.  This is caused by the files being on the host Windows system with DOS file encoding, despite running within the Vagrant Linux environment (via a synced folder).  To resolve this, [[https://stackoverflow.com/a/5514351|set each *.sh file's encoding to unix format]]. 
 +
 +:!: Windows users may also encounter errors about the inability to create symbolic links (especially when indexing MARC records). This problem is caused by permission issues related to symlink creation and can be worked around by running Vagrant from a command prompt with administrative rights. If you continue to have problems after correcting permissions, make sure you do not have an empty directory at $VUFIND_HOME/solr/vendor/.solrj -- a partially created SolrJ symlink collection can break the indexer; simply remove $VUFIND_HOME/solr/vendor/.solrj and try import again, and things should work.
 ==== Notes on File Mapping / Locations ==== ==== Notes on File Mapping / Locations ====
  
Line 49: Line 54:
   * vagrant destroy - completely destroy the VM; you will have to reinstall it (see above) if you want it back.   * vagrant destroy - completely destroy the VM; you will have to reinstall it (see above) if you want it back.
  
-===== Other Options ===== 
- 
-If you are on a version of VuFind older than 4.1, or if you want to explore other options, here are some other VuFind/Vagrant options: 
  
-  * Mark A. Duffy has contributed a VuFind 2.x Vagrant configuration [[https://vagrantcloud.com/markaduffy/vufind_2x|on this page]]. 
-  * An alternative, puppet-configured option that runs directly off a clone of the VuFind 2.x git repository is available [[https://github.com/quartsize/vufind-vagrant|here]]. 
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
installation/vagrant.txt · Last modified: 2024/02/08 18:23 by demiankatz