fmaul/vagrant-alfresco-nightly

Creates a linux VM with vagrant, installs and runs the lastest Alfresco nightly build

vagrant-alfresco-nightly

Creates a linux VM with vagrant, downloads, installs and runs the lastest Alfresco nightly build

VM

• Uses Vagrant Vitualbox provider
• Creates a VM based on Ubuntu Trusty 64bit
• VM with 4 CPUs, 4GB of memory
• Downloads latest alfresco nightly community build from http://dev.alfresco.com/downloads/nightly/dist/
• Alfresco is exposed to local port 8080

Alfresco Setup

• Standard Alfresco installation with PostgresQL
• Admin login defaults to admin:admin
• Install location: /opt/alfresco

Usage

• Checkout using

    git clone https://github.com/fmaul/vagrant-alfresco-nightly.git
  

• Optionaly add amp files or libraries to these subfolders. They are copied and applied berfore starting Alfresco.

    shared-classes/
    shared-lib/
    amps-repo/
    amps-share/
  

• Start vagrant VM

    vagrant up
  

• Wait 5-10 minutes for Alfresco being available at

    http://localhost:8080/
  

vagrant-alfresco-nightly's Issues

Reduce wget log output

Automatically run apply_amps during provisioning

Create folders
/vagrant/amps
/vagrant/amps_share

Automatically run apply_amps after Alfresco installation

Box location change

Looks like the box referenced is no longer available (see below error).

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/wily64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/wily64'
    default: URL: https://atlas.hashicorp.com/ubuntu/wily64
==> default: Adding box 'ubuntu/wily64' (v20160715.0.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/ubuntu/boxes/wily64/versions/20160715.0.0/providers/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 404 Not Found

Maybe this has something to do with the migration taking place by the host?