TURNKEYGNU / LINUX
English

Forum archive

Appliance Created : Spree

Generaltklpatch

Project home URL : https://spreeecommerce.com/
Help guide            : https://spreeecommerce.com/documentation/getting_started

base: Turnkey Core Lucid
admin email (username) : spree@example.com
admin password              : spree
Site URL :     https://IP_Address
admin URL :  https://IP_Address/admin/


During Patching some questions need to be answered

Load Sample Data? [y/n]: y
*
*
*
Create the admin user (press enter for defaults).
Email [spree@example.com]:
Password [spree]:

 

Replies (8)

feature

Reply 1

Multiple stores can be easily configured on same appliance .

Spree looks like a sweet online shop application!

Reply 2

I hadn't heard of Spree before but I just took a look at their demo site and it looks pretty sweet. I love how setting up an online business is getting easier and easier, and once we turn this into a TurnKey app - even easier!

A few comments:

  • I was delighted to see you had set up SSL support. Excellent.
  • It's best if a patch can run non-interactively otherwise we have more work to do when we convert the TKLPatch to an officially supported appliance. Is there some way to automate or disable the interactive parts of the installation? Maybe by providing default values and later documenting how the user can change them? If so we can allow the user to configure Spree on firstboot (e.g., in a di-live hook).

Thanks

Reply 3

Thaks for the tip . Let me try :)

Many ways to automate

Reply 4
Even if the script doesn't officially support pre-entering the values somehow, we could just rig its input like this:
cat answers | gem install spree --no-ri --no-rdoc
Unfortunately the things you get can away with for a TKLPatch (e.g., console access), don't necessarily hold true for the process we're using behind the scenes for the official appliances. In other words the build process has to be automatic because no user interaction is supported.

noninteractive patch

Reply 5

It is difficult to automate that part.

May be tweaking  the Rails application script will do. But didn't tried yet . Is that a critical problem. We will be mannualy applying the patch, before release , right ?

done

Reply 6
echo -e "y\n\n"|rake db:bootstrap RAILS_ENV=production

I have no idea

Reply 7

But you could try extracting the patch and trying to manually apply the conf script (perhaps line-by-line?) and see what (if any) error it is throwing.

Sorry but I don't have any chance testing it to see hwy it's not working but will try to help if I can...

Focus first on your Apache Settings.

Reply 8

The Apache settings may, for some reason, not have been updated with the Patch.  Also make sure Apache is running if the settings are good.

Beyond that, study Patches.  It is "relatively" easy to build your own.