Is Hybris installer used for demonstration purposes only? - installation

I've spent a week trying to understand how Hybris installer works and I thought I could create any type of application with recipes. However my teammate said that those recipes are useless for dev or production setup. But why installer folder is a top folder in Hybris installation? Only for demo?

Your teammate correct, installer used for creating demo system.

In the Hybris WIKI are two sites that explain this one:
Installing Hybris Using Installer Recipes
Installing SAP Hybris Commerce
But you can also just have a look into the install recipes. There is no big magic behind it. Just browse to:
hybris\installer\recipes\b2c_acc\build.gradle
(for example) and have a look into it. First it sets some properties, than it defines which extensions should be used and at last it install addons on other extensions (normally on the storefront).

Related

LXR initdb-mysql script in v2.0.0

I am trying to install LXR tp parse my working folder of linux. In some of the tutorials on the web to set it up, they are trying to use the initdb-mysql script to initialize LXR's database in mysql. Well, I can not find this script in v2.0.0 but I can see it in older versions. Is that one still valid for use with v2.0.0? If not, what script I can use to setup the db for LXR v2.0.0? or if this whole DB thing was dropped how can I proceed?
on a side note: why linux projects always lack the proper documentation?!!!! I can see they have procedure for installing LXR on their own webiste and I believe it is outdated...why not update it?
Thank you!
Don't know if you're still looking for an answer, but here is one for the record.
Creating the DB is part of LXR initialization and is considered an internal step (i.e. not end-user visible). As such, it is allowed to change along the configuration process. This is why it is crucial to follow the procedure adapted to the LXR version.
LXR 2.x is configured with a configuration wizard (scripts/configure-lxr.pl) which takes care of generating the DB structure based on a template (templates/initdb/initdb-*-template.sql). These templates are not directly usable; they must be customized by the wizard to produce an initialization script custom.d/initdb.sh which you must manually launch after the wizard has finished its job.
The whole procedure for a simple case is shown on the LXR site. From the home page, select the installation link for the version you use (note that the procedure for 1.x also applies to 2.x).
For complex cases, download and read the comprehensive user's manual from SourceForge. Once again, select the manual adapted to the LXR version.
These manuals are not outdated since the LXR project has a rule to withhold release until documentation is ready.

How to tell which modules are installed in phpBB3

I am used to Drupal, and it is fairly clear with Drupal which modules are on a server. I am new to phpBB and looking to learn just enough to migrate an install to Drupal. I can see that phpBB has 'modules' but I can't see how to tell which modules are are Installed or enabled.
From what I can see, installing modules in phpbb3 is a lot of hacking flies in the install, is this true? Is there a way to tell what is installed. even if I have to run some grep over the code?
Installing modules is 'complicated' in PHPBB3. However, anything in the MOD Database can be installed (or uninstalled) using AutoMOD. This should make your life easier if you are looking for mods in the MOD Database. The 'complicated' part of the install is any Do-It-Yourself instructions. You have to execute these by hand. This is the 'hacking files' that you mentioned. It seems to be fairly common in the 3.0.x versions of PHPBB. 3.1 is supposed to reduce this, but PHPBB development is slow. 3.1 entered feature freeze in July of 2010
A basic tutorial to install a mod using AutoMOD is available.
AutoMOD also allows you to see which modules have been installed (using AutoMOD). If you manually installed something by hacking through the install script yourself, it won't appear on this list.

CRM 2011 Online Plugin Uploader to support CI

I'm involved in developing a sandboxed Microsoft Dynamics CRM 2011 Online plugin and have a set of tests that I can drive from a xUnit front end on my local machine given that I right-click the Package and select the Deploy option (and resort to using the plugin loader sample when that doesn't work).
I'd like to be able to automate the running of my tests on my CI rig, where I'll need it to upload a fresh binary as part of each run.
We've looked at http://pluginregcrm2011.codeplex.com/ but it has bugs that prevent it working for Online and in short looks like it's no longer being maintained and I'm not keen to take ownership of what should be a fundamental tool that a platform/ecosystem should just have.
Is anyone using that tool or another plugin uploader non-interactively? Am I missing something?
I know I'm late with my answer and I`m pretty sure that you already have found a solution which is working for you.
However I felt the same pain and I have hacked a small application which could be used to simply update the plugin assembly, without doing any configuration work.
PluginAssemblyLoader -f "C:\MyPlugin.dll" -c "Url=http://crmserver/org;"
Please see http://msdyncrm-contrib.github.io/PluginAssemblyLoader
There isn't an easy OOB experience with this but the CRM 2011 Developer Toolkit just uses a set of MSBuild targets that you can call yourself. It's just MSBuild, so you could hook it into your CI build if required. If you install or just extract the Developer Toolkit MSI in the SDK you'll find the following two files in there...
Microsoft.CrmdeveloperTools.CrmClient.dll
Microsoft.CrmdeveloperTools.CrmClient.targets
As an aside it would be nice if MS would open source this as the current implementation uses predominantly sealed and internal classes within the custom tasks.

Create installation for a CMS using Codeigniter 2.0.3

I have created a basic CMS using CodeIgniter 2.0.3, and now I want to create an installation so it can work on other computers. I have hard time finding any advice on the net. What is the best practice in this case?
If you are looking for an example, download and review ionize cms. It has a good installer and is released under the Open Source MIT license.
The Ionize CMS installer is a good start, but remember it is written only to install Ionize, not for other purposes.
Anyway, it can help you to discover how to load CI classes and use them "outside" of CI.

Any existing pure PHP "make" tools?

Let me elaborate on the question...
I have a custom CMS (built on codeigniter FTW) that includes many different types of modules.
Every time we have a new project come through the door, it is a variation and amalgamation of a few of the existing modules.
Sometimes a project comes through with requirements that are not satisfied by the existing modules, in that case I will write a new module...
All the modules are separated out in folders and the code is VC-ed using GIT. Every module has it's own Model, View, Controller, SQL and Javascript files. All the dependencies are also separated and folder-ed nicely...
The next step for me is to create some sort of installer script that will take me through the "scaffolding" process step by step, allowing me to choose from the existing modules. A glorified "makefile" if you may...
Rather than rolling my own, does anyone know of any such thing out in the wild.
I know of Apache ANT (java), what I need is something in pure PHP with very low or no dependencies...
I would like something as simple as running a git pull and then php make.php
Thanks.
The "Ant-like" alternative I am aware of in PHP land is phing it is written in PHP and it will allow you to perform several tasks for packaging, deploying and testing your web applications. The documentation is a great starting point if you want to hit the ground running.
It is can also be extended to define new tasks if needed (examples and explanations are provided in the documentation)
Reading through the doco it appears to be possible to install Phing without PEAR as documented here you would have to correctly setup the environment on each machine you wish to use Phing on. I can not confirm this method though as I use PEAR for all my installs.

Resources