I am trying to migrate magento 1 website to magento 2 i am able to migrate data but i want to know is it possible to migrate code also?
The we have a migration tool kit in git hub
The toolkit covers migration of the following aspects of the Magento code:
**Module directory structure
Layout XML files
Config XML files
PHP files**
This will help you to get a over all skeleton of m1 module.
For Tool Go To
Related
I have some HTML/CSS changes I need to make on an existing project for a client. I already cloned the repository on my machine but I'm not really sure how to set it up to view the changes locally.
I'm seeing lots of files with the .gsp extension and after some googling I discovered those files mean this is a Grails/Groovy Server Pages project, which I have zero experience with (I'm a Front End Developer btw)
I already located all the HTML/CSS code I need to change, so what I need to do is learn the basic commands to get the project running locally so I can view the changes after I make them before pushing to the actual repo.
Anybody has an idea on how to set these kinds of GSP projects up on Visual Studio Code for MacOS?
Any help would be very much appreciated!
I think the easiest approach for you would be to start Grails separately using the command prompt. Identify the version of Grails for your project, and follow the instructions from Grails to setup the dev environment.
Also, remember you probably also have some sort of database to install and initialize.
I've created my first application using Openshift Tech. It's a Java Web Application running on a JBoss at Openshift and uses MySQL 5.5 as its database. And I have to deploy by it using the war file (I don't know how to do it the normal way).
So anyone can tell me: Should I create a local database or use online database? And is there another way to deploy my Java app not using the war file?
I would suggest that you check out the OpenShift Developer Center (https://developers.openshift.com), specifically this link (https://developers.openshift.com/en/jbossas-overview.html) about using jboss. Make sure you read all of the sections, specifically the Deployment Options, and the Datasources links. If you are interested in just being able to do a "git push" to deploy your code, you should create a new jboss application on OpenShift, and do a "git clone" of the code and check out how it's setup, it is using the Maven project structure, which is pretty common.
Like the question says How I should deploy a laravel project? that is already on github.
Do I need to install laravel whit the composer on the web server or just copy the whole directory of my proyect that have the folders app,public,vendor and the other files?
It depends on your server. If you hava full access to server (such as vps or even dedicated), it's good to install composer there and do laravel installation use Composer, allow you to easily manage your project later. Otherwise, yes, you have to copy all files including vendor directory to your server.
Note, if you're going to deploying to shared server which you have no full access to, you probably want to create fresh laravel installation (production version of your project) with --prefer-dist and --no-dev locally first. It'll reduce application file size.
Been wresteling with Joomla for a customer. I installed an update from 2.5.19 to 3.2.2 and it crashed. Couldn't log into the backend anymore or anything.
After putting the backup files back on the server it still kept giving errors and leaving me unable to log in.
I now have re-installed Joomla 3.2.2 and want to restore just the content (articles, components and modules).
Does anyone know where I can find the files that I should put back on the server? If I import the entire administrator folder it crashes again..
By files you probably mean database entries, as joomla contents are stored in the database. If however you do mean files then just put them in the corresponding folders e.g. images in 2.5 to images in 3.2 etc. I also assume that you probably didn't follow the correct procedure for upgrading your installation. That said I suggest taking a look at the following:
Upgrading from an existing version
What are the major differences between 2.5 and 3?
Practical Guide Upgrade Joomla 2.5 to Joomla 3.x
Upgrade from Joomla 2.5 to Joomla 3
What is the best practice for creating an installer for a winform application.
The application is supposed to install the following without connecting to internet.
.Net Framework 3.5sp1
MySQL Server
My SQL Connector
Restore Mysql db
Update Config file with the MySQL uname/pwd.
I have all the msi files for installing the above mentioned items. But am wondering about the best practice to create the installer.
Thanks in advance,
Hi I came up with a similar situation. Firstly you should have .NET framework offline installer which can be downloaded from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=992cffcb-f8ce-41d9-8bd6-31f3e216285c. I assume you are using visual studio installer. There are couple of choices but I prefer to copy the offline .NET installer to the setup projects output directory and from requirements on target machine tab I set the install URL property of .NET framework the exact name of offline setup file. As described in the figure.
So the installer does not try to connect to a remote computer to download .NET framework and install it however I think it is more appropriate that it connects to a Microsoft server and installs it. Anyways the next step is to configure the MySQL server. MySQL is really generous for me since they support a fully documented noinstall files. You can find the document here: http://dev.mysql.com/doc/refman/5.5/en/windows-install-archive.html
Using a noinstall zip archive you can copy the dbengine core files to any folder on the clint machine. And change the configuration parameters of MySQL. You can name the MySQL service anything you want. Start the the service and create tables. You can do all of this stuff from custom actions tab of the setup project choosing the appropriate script files or you can write code for it. The beautiful thing is that your customer does not need to know that he/she is installing a database engine on the target machine. I hope this helps. Thanks.