rbf7tech

[Android 4.2+][ROOT] FlashFire - Play BETA - PREVIEW - XDA Forums

http://flashfireapk.com/

MobileOdin

It's long overdue for release, but some i's still need to be dotted and some t's crossed. That being said, most of the functionality actually works well already, and it's pretty darned powerful. I have used it to update various Samsung devices from 4.x to 5.x, done (block-level!) OTAs on Nexus devices, etc.

If you're fairly tech-savvy and/or used to Mobile ODIN I suspect you won't have much trouble getting around with this app. Updates and the manual (which would be bloody useful, wouldn't it?) are coming over the next few days and weeks.

Notes and hints to help you use it:
- No kernels or recoveries are flashed for FlashFire to run, Android is torn down and restarted in a minimalist manner for the flashing part of the app to run. I'm sure this will completely fail on some devices.
- A lot(!) of memory is used, likely the entire operation will fail on low-memory devices. I strongly suggest you make an 'ID' backup as the very first test and see if that works at all.
- Technically it should be compatible with 4.2, but note virtually all of the testing so far has been done on 4.4 and 5.0 firmwares.
- SuperSU is required, unless you are running a CM-based ROM
- While development has focused so far on Samsung and Nexus compatibility and features, it should be able to function on many devices. Specific support for some other manufacturers is coming via updates soon.
- Individual files need to be named correctly (after their partitions) to be flashable or be contained in archives. Archive-wise, TAR and ZIP are supported. Compression-wise, ZIP, GZIP and BZIP2 are supported. These can be embedded inside each-other, so yes, you can directly flash the standard ZIP-inside-TGZ Nexus firmwares, as well as TAR-inside-ZIP Samsung firmwares. More formats are to come.
- Backups can be to internal, external (sd) or USB storage. The backups are compressed. There is no way of knowing if the backup will fit, you are not warned about this.
- Backups are standard TGZ's for file-based, and plain GZIP'd for raw partitions
- For block-level OTAs, flash a stock system partition or restore a (raw!) system (and vendor) backup before applying the OTA. After the OTA action, create a (raw!) backup of system (and vendor). The latter will be restorable to apply the next OTA.
- The embedded SuperSU version installed by EverRoot is v2.49 BETA

- Pro version is unlocked if you have Mobile ODIN Pro installed, but you still see an upgrade option. This is a (much cheaper) In-App Purchase you can optionally do, so you don't need to keep MOP installed.
- Pro version actually does nothing different at the moment.

In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.

If you are reading to start messing around with it, this is how you get the BETA:
- Join the G+ community using the same Google account as you're using for Play on your phone/tablet here:https://plus.google.com/communities/...25291346007584
- Sign up to receive the BETA versions from Play here: https://play.google.com/apps/testing/eu.chainfire.flash
- Use the link provided after sign-up to download the app. Note that it may take minutes to even hours before the provided link actually works.

If you have no idea what any of the above means, you might want to wait with playing with this until proper instructions are available, and more people have tested it.

How To Setup Multiple Magento Stores — Crucial Web Hosting

alternative link and instructions
https://www.properhost.com/support/kb/30/How-To-Setup-Magento-With-Multiple-Stores-And-Domains

very nice.

you must have to make things easier the domains pointing to the same DOCUMENT_ROOT

then change index.php

There are numerous ways to setup multiple Magento stores that all share the same codebase and backend, but what method you use depends on your needs.

This article is written with cPanel in mind, though the methodologies listed below apply no matter what control panel you're using. You will need Magento 1.4.x or greater installed too.

Jump To Section

URL Structure

The actual URL structure of your stores is a matter of personal preference. You can, for example, have two entirely different stores running on the same domain that share the same instance of Magento:

mall.com/shoes
mall.com/shirts

These stores could also be setup on their own domain and still share the same instance of Magento:

shoes.com
shirts.com

Another example would be a mall type setup, where your primary domain is the portal to access various stores:

mall.com
shoes.mall.com
shirts.mall.com

Regardless of the URL structure, the method for setting this up will pretty much be the same, and the result is what we're really after, which is to have one codebase for all of your stores, and one backend to manage all of these stores from.

Shared Hosting Caveat

If you want each store to have it's own SSL certificate and don't want to share a single checkout, e.g. you don't want visitors leaving domainA.com to checkout on domainB.com, then you will not be able to do this in a shared hosting environment.

The reason why you cannot do this is simple. In order for a website to have an SSL certificate, it requires a dedicated IP address.

There's no way to allow an addon or parked domain in cPanel to have its own IP address. Instead, it shares the IP address of the primary domain.

You probably think you could sign up for two shared hosting accounts, so each one has its own dedicated IP address, but that won't work either.

Since it's shared hosting, there are security measures in place to prevent one user from reading the files of another user.

So for shared hosting clients, you're limited to the following scenarios:

All of your stores do not have a secure checkout, which is fine if you're using PayPal, Google Checkout, or a similar third-party service that handles the processing of card data on their website. For example, visitors to any of your stores are redirected to a third-party website for card processing.
All of your stores are setup as sub domains, and you've purchased a wildcard SSL certificate.

If you do need an SSL certificate for all of your domains, you will need to be in a dedicated hosting environment, such as our Split-Dedicated platform. In this type of environment, we can install a multi-domain or UCC certificate.

Adding Another Store In Magento

The first thing we need to do is setup our second store in Magento.

We're going to do a hypothetical here for the naming conventions, and assume we own shirts.com. Adjust the values accordingly for your own store.

Login to the Magento admin.
Go to the Catalog tab, and select Manage Categories.
Click on the Add Root Category button on the left.
On the right, for the Name, we'll enter Shoes.com. Set the dropdown to Yes for both Is Active and Is Anchor.
Click the Save Category button.
Go to the System tab and select Manage Stores.
Click on the Create Website button.
For the Name, we'll enter Shoes.com, and for the Code, we'll enter shoes. We'll use this value later, so don't forget this!
Click the Save Website button.
Click on the Create Store button.
For the Website, select Shoes.com from the dropdown. For the Name, we'll enter Main Store. For the Root Category, select the Shoes.com from the dropdown.
Click on the Save Store button.
Click on the Create Store View button.
For the Store, select Main Store from the dropdown, making sure it's for the Shoes.com website. For theName, we'll enter English. For the Code, we'll enter shoes_en. For the Status, select Enabled from the dropdown.
Click the Save Store View button.
Go to the System tab and select Configuration.
For the Current Configuration Scope (located on the top left), change the dropdown menu from Default Config to Shoes.com.
Select Web from the sidebar on the left under the General heading.
For both the Unsecure and Secure sections, uncheck the Use default box next to the Base URL item, and enter the URL for your store, e.g. http://www.shoes.com/. Don't forget the trailing slash!
Click the Save Config button.

Now that we have our second store setup, you'll need to choose one of the following methods for actually setting up the store on the server-side so visitors can access it.

If the URL structure you've chosen will have different domains for each store, the parked domain method is the fastest and easiest method.

Parked Domain Method

For this method, we'll pretend we own shirts.com and shoes.com. The shirts.com domain is our primary domain, and Magento is already installed on it. Here's how we would set this up for the shoes.com domain:

Login to cPanel for your domain and click on the Parked Domains icon.
In the input field, enter the domain name that you'll be setting up as a second store, e.g. shoes.com.
Click on the Add Domain button.

Open up the index.php file for Magento and look for this line (it's the last line of the file):

Mage::run($mageRunCode, $mageRunType);

…and right before this, we're going to add the following code:

switch($_SERVER['HTTP_HOST']) {
    case 'shoes.com':
    case 'www.shoes.com':
        $mageRunCode = 'shoes';
        $mageRunType = 'website';
    break;
}

If you have more than two stores, you will need to add additional cases to the above code block, e.g.:

switch($_SERVER['HTTP_HOST']) {
    case 'shoes.com':
    case 'www.shoes.com':
        $mageRunCode = 'shoes';
        $mageRunType = 'website';
    break;
    case 'hats.com':
    case 'www.hats.com':
        $mageRunCode = 'hats';
        $mageRunType = 'website';
    break;
}

Addon Domain Method

This is the same scenario as above, except it takes a little longer to setup. This method might be more useful to you if, for example, you wanted to have a blog on one domain, but not on the other. You couldn't do that with a parked domain. Here's how we would set this up for the shoes.com domain:

Login to cPanel for your domain, and click on the Addon Domains icon.
For the New Domain Name, we'll enter shoes.com. cPanel will automatically fill in the next two fields, so remove public_html/ from the Document Root field, leaving us with just shoes.com. This step isn't required, but for organizational purposes, it makes more sense.
Set a password for this domain and click on the Add Domain button.
Login to your site via SSH, and go to the directory that we previously set in the Document Root field above when adding our domain. In our case, we would do the following:
```
cd shoes.com/
```
Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
```
cp ../public_html/index.php ../public_html/.htaccess .
```
Open up the index.php file and look for this line (it's the last line of the file):
```
Mage::run($mageRunCode, $mageRunType);
```
…and right before this, we're going to add the following code:
```
$mageRunCode = 'shoes';
$mageRunType = 'website';
```

Lastly, we need to create symbolic links to point to a few directories:

ln -s ../public_html/app ./app
ln -s ../public_html/errors ./errors
ln -s ../public_html/includes ./includes
ln -s ../public_html/js ./js
ln -s ../public_html/lib ./lib
ln -s ../public_html/media ./media
ln -s ../public_html/skin ./skin
ln -s ../public_html/var ./var

Sub Domain Method

For this method, we'll pretend we own mall.com, and it's setup as a portal that links to the various shops within the mall. Magento will be installed on the mall.com domain, and all of the shops will be in sub domains, e.g.:

shoes.mall.com
shirts.mall.com

Here's how we would set this up for the shoes sub domain:

Login to cPanel for your domain, and click on the Sub Domains icon.
For the Sub Domain, we'll enter shoes. cPanel will automatically fill in the next field, so removepublic_html/ from the Document Root field, leaving us with just shoes. This step isn't required, but for organizational purposes, it makes more sense.
Click the Create button.
Login to your site via SSH, and go to the directory that we previously set in the Document Root field above when creating our sub domain. In our case, we would do the following:
```
cd shoes/
```
Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
```
cp ../public_html/index.php ../public_html/.htaccess .
```
Open up the index.php file and look for this line (it's the last line of the file):
```
Mage::run($mageRunCode, $mageRunType);
```
…and right before this, we're going to add the following code:
```
$mageRunCode = 'shoes';
$mageRunType = 'website';
```

Lastly, we need to create symbolic links to point to a few directories:

ln -s ../public_html/app ./app
ln -s ../public_html/errors ./errors
ln -s ../public_html/includes ./includes
ln -s ../public_html/js ./js
ln -s ../public_html/lib ./lib
ln -s ../public_html/media ./media
ln -s ../public_html/skin ./skin
ln -s ../public_html/var ./var

Subdirectory Method

This is the same scenario as above, except all of the shops will be in subdirectories, e.g.:

mall.com/shoes
mall.com/shirts

Here's how we would set this up for the shoes subdirectory:

Login to your site via SSH, and create a subdirectory where your second store will be:
```
cd public_html
mkdir shoes/
cd shoes/
```
Copy the index.php and .htaccess file from the directory where Magento is installed, which would be in our root web directory:
```
cp ../public_html/index.php ../public_html/.htaccess .
```
Open up the index.php file and look for this line (it's the last line of the file):
```
Mage::run($mageRunCode, $mageRunType);
```
…and right before this, we're going to add the following code:
```
$mageRunCode = 'shoes';
$mageRunType = 'website';
```

Managing Multiple Stores

It's very important to remember that now that you have multiple stores to manage from one admin panel, that you make sure you're changing the configuration for the appropriate store.

In the System → Configuration section, if you leave the dropdown menu for Current Configuration Scope set to Default Config, it will globally change the values for all of your stores, assuming you haven't removed the checkmark next to Use default throughout the configuration sections.

You can change the configuration values globally, for each website, and for individual store views.

Secure Checkout For Each Store

For those of you in dedicated hosting environments, you can follow either the addon or parked domain method from above, and edit the httpd.conf file to give the addon or parked domain a dedicated IP address. However, this is not advised. Your changes will most likely be overwritten with a control panel upgrade, Apache or PHP rebuild, or even simple maintenance.

Your best bet would be to purchase a Unified Communications Certificate (UCC), also known as a multi-domain or multiple domain certificate. If you're on our Split-Dedicated product, after you've purchased and installed this certificate, we can make the necessary changes to support this type of certificate (this is something we have to do, since it's not natively supported by cPanel). Once we have the SSL setup, you simply follow the parked domain method for each domain you've assigned to your UCC certificate.

This is just one of the many advantages of running your online business in a more secure and flexible hosting environment like this.

Once you've done the above, all of your stores will have their own secure checkout and will still share the same codebase and backend for management purposes.

rbf7tech

terça-feira, setembro 22, 2015

FlashFire is the spiritual successor to Mobile ODIN

sexta-feira, setembro 11, 2015

How To Setup Multiple Magento Stores