I've got a wordpress multisite installation that's hosting enough blogs I need to shard the database. I see there are three plugins available to spread wordpress across multiple databases:
http://wordpress.org/extend/plugins/hyperdb/
http://premium.wpmudev.org/project/multi-db
http://wordpress.org/extend/plugins/shardb/
I'm trying to decide which one to use, but I haven't really found much info comparing them[1].
Does anyone have experience deploying any of these three tools? Or better yet, experience with more than one of them and a rundown of why you switched.
Thanks,
Bethany
[1] http://mu.wordpress.org/forums/topic/16244
It looks like the wordpress action is over here on this nice wordpress stackechange site, check it out:
https://wordpress.stackexchange.com/
And here's an answer to this question, over there.
https://wordpress.stackexchange.com/questions/2825/wordpress-sharding-which-multi-db-plugin-to-use
Related
I own a webpage which has wordpress.org preinstalled.
I have never done anything with it, but now it's about time. As I'm learning django, I would like to build my webpage with it instead of using the preinstalled wordpress.
How do I go about it? I haven't found anything related to this topic searching the internet.
This is the webpage with preinstalled wordpress I'm talking about.
I did the same just 9 months ago ... you can literally start from scratch as you seem to not have too much on the wordpress page its not a big damage. Next steps: you can check if the theme you used is also available for html5 so it looks familiar and you need to choose a provider who hosts django unless you dont want to setup the server yourself. Any questions ... just ask.
I've a bit of a problem. I'm currently trying to realize a WordPress development process regarding to one of my old question / topic:
Wordpress development process
So currently I've GitLab installed (which is a free and good solution for small projects). On GitLab I've 3 branches: prod, staging, develop.
Regarding to these 3 branches, I've 3 instances of WordPress running.
Everything works good (Branching, updating files and all the stuff) until I need to make a plugin update. The problem is, that I only want to do updates on my develop instance in the future. So when I do an update, I can push all updates files to git. But there is a huge problem - the database.
I've tried to do some research to find out if there is any tool to make my databases working like GIT but I can't find any Open Source Tool which seems to be good enough to handle this task. There is a plugin for this, but I don't want to use a plugin.
So I hope there is a better solution to perform a continues delivery process like this here in WordPress:
Does anyone have experience with this kind of process within WordPress? If yes, how do you handle this to be 100 % safe with developing and updating WordPress?
I'm thankful for any ideas / help / experiences I can get!
I have reviewed your question and the visual diagram that you have presented over here. I have also done lots of thinking on this process to build the WordPress website with the powerful development process and start doing research on google.
After some days I get to know a very good system which absolutely follows the above process by default. The name of the tool is roots.io
We have used this system on our local and on the server for some of our clients and they also fill like this is an absolutely perfect and secure tool for use. It is a little bit tough and difficult to install but after installation, you will see this is absolutely game changer tool for WordPress website development.
Best Feature:-
This tool installed the operating system and manage via virtual machine and create an environment as you have on the live server called 'trellis'.
They are using WordPress boilerplate with modern development tools, easier configuration, and an improved folder structure called 'bedrock'.
They use sage theme with SASS based platform which is very powerful.
Even if the client can not able to install any plugin or edit the code from the theme editor, related to coding we only need to operate through the local development environment.
It also has multiple staging environments like:-
Development
Staging
Production
You can review some more details from here: https://roots.io
I hope this will help you to find your solution as I got my solution by using this.
Thank you
I search for easiest way for migrating from custom CMS builded upon PostgreSQL to WordPress CMS.
I don't search for ready-quick answer, but some guidance, approach explanation etc.
Also, if someone here is sure that his approach is successful, then we can work together (with some money arrangement).
Thank you
At first, this question appeared to be too trivial to me to actually require a Stackoverflow post. However, after executing many Google searches for the information, I am at a lost when trying to figure this out about Couchbase.
In Couchbase (I am using the 2.2 Community version), how do I share views among developers? Is there some sort if import/export functionality available? If not, then how does Couchbase intend for developers to share the views that they are using without needing to do manual copying/pasting? It is obvious that the code that a development team would write for querying Couchbase will require accurate view names. Without having a way to send a developer a view file, to accurately setup a Couchbase DB, how can it even be possible to develop with Couchbase locally as a team?
I'm sorry if I sound a little desperate or harsh here, but if it isn't possible to share views among multiple developers, then I don't see how Couchbase can be a viable DB solution for a team of developers trying to share database configuration, similar to how a team using an SQL DB would share schema files to set up the DB.
Several ways you can approach this:
1) Create views programmatically as demonstrated here in java:
http://tugdualgrall.blogspot.com.es/2012/12/couchbase-101-create-views-mapreduce.html
or here in node.js:
http://www.tuicool.com/articles/RvYbQn
2) Store all your views in your version control system (This is the option I use). If you are developing locally then only you need your personal view code, once they are working and your tests are all passing then you can check them in.
I assume you'd then be developing on an testing environment so yes sadly here you'd have to update the views either by hand or by using option 1.
You could also take a look at perhaps using this tool but only for views: http://www.couchbase.com/communities/q-and-a/how-bulk-import-design-docs-and-views-couchbase-server
This functionality currently is not available in the admin UI.
There is a defect/enhancement open Ability to import/export views MB-8436. You can leave there your feedback and vote for it so it will be included in the next release.
In the meantime you can use Design Document REST API
Also there is a workaround blog
I like taxonomies in Drupal and thinking about building a CMS on it for a website that has been online for years. I'd like to leave the database AS IS (it's mySQL) to make sure the old CMS works as well - some people who use it aren't willing to learn new stuff. The website in question is a products catalog and I'd like to extend it to also manage orders, inventory, samples and QA documentation.
It seems that using two databases - one for drupal itself and the other for data - has other pros as well. It's like separating model from view.
I'm not a frameworks kind of guy - I rather like to do things from scratch employing only minimal number of dependencies and intermediary layers. I like the Drupal's approach and appearances though.
Is Drupal the right tool for the job? How easy is it to use it with existing database without importing all the data into drupal's db? Am I going right direction? Thanks a lot!
I think it is nearly impossible to reuse the existing database as is with Drupal.
If you still want to use Drupal, there is a rather sophisticated module to help moving the data to a database Drupal will like: http://drupal.org/project/migrate