I have a deployment system where updates are performed locally and pushed up to production using Git and CI. Now I do this ok with Wordpress and Drupal as they both have the option of upgrading the database on the production server. However I can not find how to do this on Joomla. I do not want to copy the database from my local to production. It needs to be sync down only as users are making changes as I am doing the upgrade.
Related
I am currently working on a project where I use Postges inside a Docker and manage it via Flask-Migrate but only during development.
My goal is to use a database directly on a VPS in production.
Can I create migration scripts on the Docker databse and then copy them to run on the VPS database?
Your migration scripts will be stored with your source code, not inside the Docker container where the database is. So it really does not matter, as long as you set the database connection URL properly you can generate and apply the migrations on any supported database, be it hosted on a container or a VPS.
I recently followed a tutorial on getting started with WordPress which included installing a WAMP Server.
Some days later I checked on a Java program that I'm working on which connects to a local database, but it could no longer connect to that database, and if i checked in the MySQL WorkBench or DataGrip it seemed as in that database did not exsist anymore, and it only showed my database from my WordPress project, all the other local databases i had made before installing WAMP are gone.
Is there any way to find them?
EDIT: They DO exist in the folder C:\ProgramData\MySQL\MySQL Server 5.7\Data but I don't know how to access them, as they're not working in my Java program, or not showing in the WorkBench as schemas anymore
You now have 2 MYSQL Servers installed and therefore which ever one is started first will be the one that phpMyAdmin or Workbench talks to.
To get to your old database, just stop the wampserver MySQL server
[left click] wampmanager -> MYSQL-> Service Administrator->Stop Service
Then go into the services snapin
Windows Key+R
Enter services.msc
Press the OK button
Find the service called MYSQL and start that.
You should now be able to access the old database using phpMyAdmin or WorkBench
Backup the old database
Then from the services snapin agian STOP the MYSQL service.
Restart the WAMPServer MySQL
[left click] wampmanager -> MYSQL-> Service Administrator->Start Service
Now restore your database into the WAMPServer version of MySQL.
Once this is completed, you can uninstall the old MySQL Server instance.
While waiting for a MSSQL backend compatible with Django 1.6, I've been doing development using SQLite and using South to keep my models synced with the DB.
Now that django-mssql v. 1.5 (which supports Django 1.6) is available, I'd like to move my Django models to a SQL Server database. Note that there is only test data in my SQLite database, so there's no need to migrate the data - I'm only interested in implementing the models in SQL Server, and using South to implement schema modifications going forward.
I think the proper procedure after installing django-mssql is:
Change the settings.py to point to the MSSQL database per the
django-mssql installation instructions
Remove all of the existing South migrations and the migrations
folder
Run manage.py syncdb
Run manage.py schemamigration --initial <application_name>
Run manage.py migrate <application_name>
Have I missed anything?
We have recently migrated to using the Visual Studio database projects. What we want to do is for the database to deploy when the TFS build server builds.
This is relatively simple and we have this working for a single database, however, what we need is for it to deploy to multiple database as we have a SaaS product with multiple databases. So for example, when we do a QA build, all the different databases with various configurations on the QA DB server should be updated.
Is there a 'proper' way to do this?
Our current plan is to take the deployment .sql script that will be generated from the database configured for deployment, then create a custom build task which runs this script against the rest of the databases.
I don't think there is a standard way of doing this, so we created a custom build task that iterates over the databases we want to deploy to executing the deployment script generated by the standard database project's deploy against each DB.
I followed the excellent tutorial on
http://www.jakusys.de/blog/2008/09/grails-and-liquibase-how-to-use/
in regard to my dev database on local machine where grails is installed. All went well.
Now I want to deploy grails war to remote website where I setup mysql on remote server.
But I am at loss now. How do I apply the command:
grails migrate
so that the now the remote database has the DATABASECHANGELOG table.
In the database there is some production data that I will manually copy from my local mysql to fresh install of remote mysql database while most of other tables are fresh and have no data. I am waiting for reply to this question to make sure I don't mess up something before actually launch my grails application on remote production server.
You can migrate a remote DB from your computer, using grails.env variable, like:
grails migrate -Dgrails.env=production