Till recently i've needed to run the dev environment for my Heroku (postgres) app on mySQL.
Obviously this is not ideal (running dev and production on different dbs) and, as the original restriction has been taken away, i'm looking for the best strategy/instruction-set for moving my dev environment over to postgres and either migrating the mySQL data across, or pulling the production data into the new dev db.
What is the best route?
Thanks in advance for any help or direction!
Best bet is to take the simple route.
Install postgres
Setup your local codebase to look at the new
database
rake db:setup
heroku db:pull --app <your production app>
Related
My company has two web based project. Our main project (Starbooks) was built using xampp server and Codeigniter framework that installed in our Windows OS and the second project (Frontlearners) was built in Lamp server and moodle (LMS) framework with Postgres database that installed in ubuntu platform.
My goal is to collide this two projects into one by moving the second project (Frontlearners) into the main project (Starbooks) server which uses with xampp server windows platform.
My first attempt is to export the moodle Postgres database using PGAdmin then move the moodle project to the main project server on windows. But I don't know if this is the correct way or not because Postgres and mysql are different database type. I've searching across the internet hoping for the answer or tutorial related to my problem but the results are always fresh installation of moodle which is not related to my problem.
Anybody knows how to solve this problem, a tutorial link, or any article about this situation?
There is a database transfer tool in Moodle.
https://docs.moodle.org/311/en/Database_transfer
So you can convert the PostgreSQL database to MariaDB
First ensure MariaDB is installed on Ubuntu
Turn off cron and put the site in maintenance mode
Then go to Site administration > Development > Experimental > Database migration to convert the database.
Or direct to /admin/tool/dbtransfer/index.php
The tool will check the database structure matches the structures in the install.xml files. If there are any differences, then you will need to update the relevant install.xml file or database table before continuing.
If its a large database, then the UI will probably time out. So use the command line version instead:
php admin/tool/dbtransfer/cli/migrate.php --help
Having said all that, IMHO I would transfer the Windows project to Linux.
I have setup KIE workbench and everything is running fine. I am unable to understand how to manage the deployments in the production environment. I have to do two things.
How to manage users/roles/groups in dev and prod environment. I have users/roles/groups and project setup in dev environment. Is there a better way to deploy the same settings to production?
I have created some rules in dev environment. What is the best way to backup my data and deploy on production.
I can speak from experience. I have installed KIE Workbench both in dev as in prod. I've used the same method to manage the users/roles in prod as well as in dev.
As for the rules, what I do is I clone the repository from the dev environment to my local machine and then I upload the files individually to the workbench in prod (e.g., drl files). It is not very efficient but it works.
I am starting work on a website that will use MariaDB for storing information (no sensitive information), and would like to keep everything in my git repo.
Originally, I planned on installing MariaDB to the separate computers that I plan to develop on (my desktop and laptop), but decided that it may be easier to store all of MariaDB (the program and the databases) in the git repo, so that one would just need to clone the repo and run MariaDB from the repo just like they would run Node, but I have not found any information on how to do this.
My questions are (1) should I install MariaDB and its databases to my git repo, instead of installing MariaDB in /usr, and the database in /var/lib/mysql, and (2) how would one do that?
Instead of attempting to put a mariadb runtime environment inside your version control, consider using docker to describe how to configure an appropriate mariaDB installation. I use makefiles atop that to contain the commands I use to build and run the docker but you coould just as easily use a shell script. Finally, provide a dataabase load script that loads your test database from a text file within the repo.
using docker to describe runtime environments for your application and dependencies is awesome. It strikes a great balance between having an incomplete git repo, and having to put binaries and database data in your version control. You wouldn't want to track changes to the underlying maria db files, anyway, so best not to commit them. You can build the docker containers you need on every workstation you use without much trouble, your automation around creating them provides a mechanism to ensure consistency, and by loading a database with the correct test data every time you develop your app, you'll have a better development process and less schema and data related changes. It works great, I do nothing but docker driven development these days.
I have a VPS with Liquidweb, which currently uses a standard LAMP stack. I want to replace/supplement the installed version of MySQL with Percona, specifically to leverage XtraDB's advanced features. My initial request to their SysAdmins was they don't support that since its a nonstandard install.
My question is has anyone successfully run Percona in a WHM/Cpanel controlled environment? How did you install Percona? Did you have any problems? How do you maintain that installation? Were you able to have WHM "automatically" upgrade Percona, or at least prevent it from upgrading Percona down to MySQL? Is there a better way?
As a background, I am a software developer. I can run make, but managing a secure DB installation is beyond my scope.
http://www.ecommy.com/linux/install-percona-in-a-whm-cpanel-environment
also:
http://forums.cpanel.net/f5/installing-percona-mysql-track-queries-per-user-table-access-volumes-103477.html
The install is pretty straight forward. The database upgrading will not be managed within WHM/cpanel, so you would need to use your own method to administer updates. You should be able to install Maria in about the same matter.
I would personally keep a close eye on the installed database when cpanel does an update, just to make sure that it doesn't do something crazy like kicking the Percona version out. But, it should work without too much fuss.
Is this a right thing to do? I am using the Apache/Tomcat that comes with the liferay portal bundle and I used the MySQL that comes with WampServer at home but now I want to transfer my portal to a real Server and I wanted to know whether I could still use the Wamp's MySQL or should I install a real MySQL (What's the difference?)
Thanks in advance.
WAMPS MySQL server is not artificial, its the real deal. WAMP just bundles these softwares together and lets you deploy easily for development purposes. In a production environment you would deploy MySQL as a separate software and tweak it according to your needs. You CAN you WAMP on production environment, however you will need to make sure that you do not have any security flaws in there.