First run/boot experience

[karlitschek]

I think the first run experience after booting the VM should be like that:

• The Linux system boots including MySQL and Apache
• ownCloud should be preinstalled with a working DB setup.
• The output in the console after booting should be:
  • Welcome to ownCloud. Your server is now ready!
  • Please go to http://xx.xx.xx.xx to access ownCloud
  • Your ownCloud admin account is: login:xxx passwd:xxx
  • You Linux root password is: xxx
  • More information in the documentation at: http://doc.owncloud.org/....

Would be great if we could make this happen.

[enoch85]

After some testing I think it's best to create every script separate to eachother and then link the scripts with ìnline when building the appliance. Here is the welcome script: https://github.com/owncloud/vm/blob/master/enoch85-testing/welcome.sh

My wish is to cat <<- WELCOME > "$welcome_sh" and then add whatever text you want, but Vagrant doesn´t seem to accept that. It gives me errors with the shebang for example and thinks that it´s a directory. Here are some more info about inline: http://docs.vagrantup.com/v2/provisioning/shell.html

Maybe I have to sed -i all the lines seperatly into that file?

Btw, sorry for committing changes to the master branch, took me a while to figure out that I can do the testing in a separate branch. ;)

[jnweiger]

On first glance, your first line '#!/bin/bash/' should not have the trailing '/'. Cannot spot anything else right now.

Inline code modelled after http://docs.vagrantup.com/v2/provisioning/shell.html#inline-scripts worked just fine for me in e.g. https://github.com/owncloud/vm/blob/master/vagrant/Vagrantfile

No need to do testing branches right now. Let's use this repo as a playgound, until we have somehting working. Then we cleanup.

[enoch85]

@jnweiger I tried to remove the shebang completley yesterday, and it still didn't work. Feel free to test it yourself. Here is the file: https://github.com/owncloud/vm/blob/testing/enoch85-testing/ubuntu/Ubuntu14.04.sh#L45

[jnweiger]

@enoch85 I've commited a fix here https://github.com/owncloud/vm/commit/0d04a57f769aac303feb178eb9772d644b08a479

Issues:

• !/bin/bash must not have a trailing /

• mkdir -p /var/scripts was missing, thus welcome.sh could not be created there.
• trialing 'fi' removed

Features:

• automatic version number retrival from the Packages file.
• restructured variable naming. Cleaner for me now.
• using cat << EOM for the message instead of one echo per line.

Note:

• We have all the files from the current directory imported under /vagrant. (I've added an 'ls -l' to message.h to demonstrate that). So the best way would be to have an inline '$script' in the Vagrantfile, that runs some of these files, like message.sh and or simply copies to /var/scripts/ what is needed there later. (/vagrant) is only available during build, not at runtime.

[enoch85]

@jnweiger Ah yes, nice! Was a bit tierd yesterday ;) Have you tested?

In my VM (used that as reference) I do exaclty like I did with the welcome.sh, and it worked - I tested inside the vagrant VM, and it worked there as well. But it doesn't seem to work during the build.

What you are saying is that it´s not possible to create files with cat << EOM inside the VM with vagrant, during the build? In other words, the files must be added later? I want it to be fully automatic.

Otherwise we have to add all the scripts in one file single, and it would be cleaner to create them seperatly and then link them (like I did) to a gist or something like that. In the future it would be easier to overlook each script, instead of doing all the changes in the same file. Do you agree?

[jnweiger]

What I tried to say:

• cat << EOM works fine as an alternative to one echo per line.
• no file has to be added later. All is fully automatically :-)

What exactly did not work during build?

[enoch85]

@jnweiger Ah ok, I misunderstood. and yes, I agree that EOM is better. Forgot to remove the echo yesterday and now I see why it didn't work. :)

I´m at my work now, will try later tonite. Meanwhile it would be very cool if you could take a look at this list: https://github.com/owncloud/vm/issues/6

All the files that I use in my VM is published under the testing folder I published yesterday. Including the conf file for self-signed SSL (maybe we have to forward port 443 as well?) https://github.com/owncloud/vm/tree/master/enoch85-testing/ubuntu

Btw, can you merge the changes and delete the tesing branch? THX

[enoch85]

@jnweiger FYI, merged the commit and deleted the testing branch. Are you availible on chat in 2 hours? Was thinkinig we could start building this for real. Would be nice if it was ready until the conference. Btw, you are coming, right?

Edit: My nick on the IRC channel is: enoch85

[jnweiger]

I am coming to Berlin and looking forward to meeting you there! I am offline in a few minutes for today. sorry. Sent you some friend requests and stuff. Or look for jw on freenode later.

[enoch85]

I can confirm that this is fixed! :+1:

@jnweiger Now we have to combine welcome.sh with the ownCloud install and setup during the build. Don't know why you seperated them? Anyway, closing as this is fixed. Woha!

cc @karlitschek