You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2021. It is now read-only.
Package and ship alfresco-spk as a Vagrant plugin; it must be possible to install it using the command
vagrant plugin install vagrant-alfresco-spk
Plugin can be configured using the same syntax in Vagrantfile:
if Vagrant.has_plugin?("vagrant-alfresco-spk")
config.alfrescospk.stack_template_url = "file://#{ENV['PWD']}/stack-templates/clustered-enterprise.json"
#TODO - add syntax for instance template overlays
end
The text was updated successfully, but these errors were encountered:
Not sure. Anything that makes it easy sounds good to me, but ever more layers of abstraction might be harder to understand.
My use-case is that I'm trying to put together an all-in-one (including DB) docker image to test an alfresco client with some automated tests. I want to just fire up the image, load some data, read it back out again, and kill the image; without multi-container complexity. And I'd like to be able to update it quickly and easily as newer version are released. I'm not sure if alfresco-psk is the best way to get there, or if I'm better off with just a suitable Dockerfile. I tried https://github.com/makuk66/docker-alfresco which gets there, but takes a long time to start up: 6min as-is, which I could get down to 3.5, but I want <1, and the run-time installation prevents that. Now I'm trying alfresco-psk, but haven't succeeded yet; and having to install vagrant/python pre-requisites for packer are a little bit of a nuisance.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Package and ship alfresco-spk as a Vagrant plugin; it must be possible to install it using the command
Plugin can be configured using the same syntax in
Vagrantfile
:The text was updated successfully, but these errors were encountered: