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.
Related
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.
Hey all,
I'm new to linux and still learning and I've searched and haven't been able to find the exact same issue anywhere......
I have a CentOS remote server hosting approximately 60 websites. Some just html, others custom scripts, and mostly wordpress.
I want to backup ALL the sites to my local Ubuntu 16.04.1 lamp stack server.
I am using Filezilla and I'm assuming it's not downloading the the /var/www folder because of permissions, but again, I'm new and don't know much.
Questions:
Do I need to change some settings in Filezilla?
Can I download them with terminal but in bulk?
I do understand I will have to grab all the databases and install them locally, separately, but are there any programs that could help automate this process, paid or free?
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.
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>
Extended title: How to setup a box with (Windows7 + Apache + VisualSVN + MySQL + PHP) and 3 machines with (MacOs/Windows7) and Dreamweaver CS5 as a web development environment for a small team
These are my thoughts. Please forgive my ignorance, I still don´t have completly clear all the concepts.
1. I need to setup a web development environment for a small team of 3 web developers. The staging and live environments will be in a remote server under an external hosting company (probably Amazon).
2. Our first project is a blog with Wordpress
3. I've installed XAMPP in the box and can be accessed like this (http://dev.company.com/xampp)
4. I've installed Wordpress and can be accessed like this (http://dev.company.com/blog)
5. I've installed VisualSVN in the box and can be accessed like this (http://dev.company.com:8080/svn)
6. I don´t know how to import files for the first time to my repositories in the box (c:/repositories/blog)
7. VisualSVN includes Apache. I don´t know if I should turn off the Apache of XAMPP or if should install another version of VisualSVN without Apache
8. I don't know if I should keep my repositories at C:\repositories or c:\xampp\htdocs.
9. I've read something about hooks? to copy the files from the repositories to the htdocs? Can anybody explain this process?
10. Would it be a good option to keep all the files always in the box? or it is a better option to check out the files to the machines?
11. When setting up Dreamweaver to connect to the SVN Server, do I have to point to the trunk, branch or the name of the repository? Do I have to setup a different connection for each branch?
12. How can we include images and PSD's in the repositories?
When we start a new project we usually just checkout files on clients and commit the changes to the server when finished editing. This way people can just edit files on their own machine (without other users slowing stuff down).
Can't you just do a Linux install for the webserver (CentOS or something like that?). Windows 7 seems so heavy / unfitted for webdevelopment server.
We usually keep the repo out of the webroot.
XAMPP really???
Just my two cents...
It's strongly not recommended to use Apache HTTP server bundled to VisualSVN Server for anything else than Subversion server. So you have to install VisualSVN Server and XAMPP.
Just keep repositories in C:\Repositories. If you move them to htdocs all repository will be accessed for everyone who have access to XAMPP.
Common practice is to checkout working copy to htdocs folder, configure permissions to deny access to .svn and then run svn update in post-commit hook in VisualSVN Server.