Thanks very much Tobia. I was unaware there was prior art using Chef.
Is there a reason / may I propose that Chef and/or Puppet with Vagrant
be the suggested development setup instead of instructions that aren't
repeatable in a reliable way across hosts etc?
[3] I'm aware of but have just avoided in the past since I store my
private boxes in other places already. For this purpose I suppose I
should use a pre-existing public box as the base is logical
[4 and 5] Also aware of these just haven't had prior experience with them
The directory setup difficulty breaks down to am I doing it right and
the 3rd party submodule behaves odd on the host system which isn't
suprising seeing as the VM checked it out the absolute paths don't match.
The directory setup I went with was
\var\www\owncloud => owncloud\core
\var\www\owncloud\apps\* => [owncloud\news, owncloud\gallery,
owncloud\music, owncloud\notes, owncloud\calendar, owncloud\contacts,
owncloud\documents, owncloud\documents, owncloud\bookmarks]
Also it should be mentioned that right now you get the vagrant vm up and
running switch the repository remotes to point to your own forks next
puppet run it points them back to github.com\owncloud\repo\master which
isn't ideal. Think I may extract the repository location to a hiera
variable with owncloud as the default.
If you spin up a VM I'd like to know everything worked for you.
Thanks,
Colin
On 2014-06-10, 11:55 AM, Tobia De Koninck wrote:
Hi
I always use vagrant for ownCloud development. But I don't use Puppet.
There is already an advanced Chef cookbook for ownCloud:
https://github.com/onddo/owncloud-cookbook
I created a Vagrantfile for Virtualbox for it [1] and for hosting on
DigitalOcean [2].
What are your problems with the synced folders? I have played a long
time with it, and find the solution in [1] the best. For DigitalOcean
you can setup an SSH connection with the VPS in your IDE. (I tested
rsync but bi-directional wasn't working for me.)
You should defenitly have a look at [3]. This is an official site from
Vagrant with a lot of base boxes. I like to use the one from chef.
These are without chef installed, so you could use them for puppet too.
Also have a look at [4], this is a build-tool from vagrant to create
base boxes. In the bento project - from the makers of chef - there are
a handfull useful scripts. [5], which generates the boxes from chef in
[3]
I'll one now spin up your vm :)
P.s. you could send your email to the owncloud-dev mailing list too.
Cheers
Tobia (aka LEDfan)
- [1] https://github.com/LEDfan/vagrant-setups
- [2] https://github.com/LEDfan/vagrant-setups/tree/oc-dev-do
- [3] http://vagrantcloud.com
- [4] https://github.com/mitchellh/packer
- [5] https://github.com/opscode/bento
On 10-06-14 15:34, Colin Hutchinson wrote:
Hey All apologies if this is in the wrong mailing list but I'm
looking for some general constructive feedback / bugs.
I'd like people's opinions / feedback on Vagrant as provisioned by a
Puppet manifest that I've been working on:
https://github.com/hutchic/vagrant-owncloud-dev
After going through the development setup a few times including via
ocdev I fealt the project needed someting more reliable /
reproducible. Right now it provisions a LAMP stack on Ubuntu 12.04
inside VirtualBox. It clones the repositories into a shared folder
which does present some challenges I still need to sort through and
I'm still not positive I have the project directories setup in the
most optimal way.
The host environment I've been using is OSX 10.9.2, Vagrant version
1.6.1.
Regards,
Colin Hutchinson
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
