Looking forward to continue to use this plugin in the future.
]]>I am just starting to learn all the power behind GIT to keep track of versions, and from that, comes a lot of questions.
I know how to use the wpcli, and I am not afraid with terminal commands.
I’d like to have advices, to learn about best practices when managing the code from github or gitlab.
First thing first :
How would you create the repository?
Would you clone? or mirror from https://github.com/WordPress/WordPress.git ?
Would you create a blank repository and install wordpress from wp cli?
Do you think it’s a good idea to be aware / keep track of every single commit from the wp dev team on wordpress? Or just the commits from our own install is enough?
I am looking forward to hearing your recommendations about that to make the best start as possible.
Thanks!
]]>So all you need is an input field in the admin interface where you can enter your own gitlab URL. Then you can also use a self-hosted Gitlab instance.
]]>What’s the best way of feeding these strings in from the ubuntu bash shell so they don’t get exported to the gitlab repo … ?
]]>https://oauth2:[email protected]/stuff/awesome
However, when I attempt to install through WP pusher I get the following error.
An error occured: Download failed. Make sure repository handle is correct and that you have a valid token.
If you are using GitHub, try obtaining a new token. What gives?
]]>gitlab is a popular alternative to github, and many developers trust it more since github was acquired by Microsoft in 2018.
Here’s a comparison between github & gitlab:
* https://about.gitlab.com/devops-tools/github-vs-gitlab.html
]]>We are developing WordPress Site lampstack running in Pivotal Cloud Foundry Container, Apache, PHP runtime, MySQL DB (configurations) and AWS S3 bucket (remote storage to store media files). This container do not have any command line access.
We have 3 different environments in separate cloud container (Dev, Test and Prod). Development is being used to develop the themes, plugins etc (non-content). We are using Elementor page builder to build our site. And we are trying to promote same changes from Dev to higher environments (test and Prod).
The plugin, theme changes (PHP, HTML, JavaScript code) are stored in Git repository, configurations are getting stored in MySQL DB and media files are stored in AWS S3 bucket.
We are able to move the changes committed in Git Repository into Test environment. Whereas unable to identify the configurations stored in MySQL DB for newly developed elementor pages.
We would like to know the possibility of identifying the MySQL DB configuration changes that are being made by elementor and migrate the configurations into Test environment. Also, we want to know how to merge the DB configurations from Test to Production without overwriting the existing live content changes.
Any help would be highly appreciated. Thanks!
]]>Currently my frontend code pulls site content straight from the WP API on page load. This isn’t really a static solution. It would be better to trigger a CI/CD pipeline that builds a completely static frontend through their API whenever someone saves a custom post.
.
It would be great if we could have an input field in custom post settings that takes the name/names of functions that will be ran on publish.
add_action('publish_customposttype', 'func_name');
By leaving implementation of the actual function up to the developer, this feature could be used to trigger all kinds of things: CI/CD Pipelines on a variety of platforms, Slack notifications, other WP core functions, etc.
.
I was inspired by this WP plugin: https://github.com/kmturley/wordpress-gitlab-trigger-pipeline/blob/master/gitlab-trigger-pipeline.php
]]>Props to Leon for the speed of development and really pushing this project forward.
]]>