Live data from Hacker News

VersionPress goes open source

blog.versionpress.net

11–20 of 23 posts

Re: VersionPress goes open source

#12

I put a client's site in a git repo once, but I never figured out how to safely and effectively git the database too. Kudos to VersionPress! I've only learned about them today but they seem to be doing a really solid job.

sql's mysqldump CLI command locally or phpmyadmin > export produce a text based db backup in SQL and version that file in git.

If it is a huge site split the tables into separate files but 1 file is pretty good for most medium sized clients.

Git merging db's can be gnarly if changed significantly, (rollbacks are trivial).

This looks very useful and GPL just like Wordpress - excellent!

Re: VersionPress goes open source

#14
post #12

I put a client's site in a git repo once, but I never figured out how to safely and effectively git the database too. Kudos to VersionPress! I've only learned about them today but they seem to be doing a really solid job.

sql's mysqldump CLI command locally or phpmyadmin > export produce a text based db backup in SQL and version that file in git. If it is a huge site split the tables into separate files but 1 file is pretty good for most medium sized clients. Git merging db's can be gnarly if changed significantly, (rollbacks are trivial). This looks very useful and GPL just like Wordpress - excellent!

basically do the same with drupal also.

Re: VersionPress goes open source

#16
post #3

Helpful info for me: VersionPress is a free and open source version control plugin for WordPress built on Git. We increase major version numbers quite rapidly, e.g., VersionPress is at 3.0 at the time of writing this, but that does not mean it is production-ready.

Maybe 10.0 will be 'production ready'

Re: VersionPress goes open source

#17
post #10

This is a problem that's bugged me for a long time - it's good to see people working on it. Deploying and managing most traditional CMSes is a nightmare, IMO. MODX has had something similar for a while with Gitify[1] for the site structure and VersionX[2] for content, but I haven't had much of a chance to use them. [1] https://github.com/modmore/Gitify [2] https://modx.com/extras/package/versionx

It's bugged me too, almost to the point of me thinking I was crazy. For the life of me, I couldn't figure out how people were handling these problems with WordPress. And frankly I'm still baffled. I'd get these looooongggg schpeles about workflows tangential to the actual problem and then finally the admission that you just write down or remember the changes you made on staging, and make them on prod as well.

Re: VersionPress goes open source

#19
post #10

This is a problem that's bugged me for a long time - it's good to see people working on it. Deploying and managing most traditional CMSes is a nightmare, IMO. MODX has had something similar for a while with Gitify[1] for the site structure and VersionX[2] for content, but I haven't had much of a chance to use them. [1] https://github.com/modmore/Gitify [2] https://modx.com/extras/package/versionx

It's bugged me too, almost to the point of me thinking I was crazy. For the life of me, I couldn't figure out how people were handling these problems with WordPress. And frankly I'm still baffled. I'd get these looooongggg schpeles about workflows tangential to the actual problem and then finally the admission that you just write down or remember the changes you made on staging, and make them on prod as well.

Exactly. VersionPress tries to automate that :)

Re: VersionPress goes open source

#20

What is your business model now that you're not charging for the software?

Charging for a GPL'd software (all WordPress plugins have to be GPL, at least in practice) is tricky and most companies in the WordPress space focus on services. Which is what we'll do as well. The technology itself, however, will be free and stay free.
Post reply on HN