Running post-deployment hooks

Igor · August 6, 2023, 5:29pm

Hi

I’ve read your documentation and I have a question regarding post-deployment hooks. For example, let’s say that I want to deploy a WordPress container and pass information about installing some Plugins and/or Themes.

What would be the best way to do that? Like building my custom container image that will have a service for such things, or maybe there is some better way?

I also need to be able to change the state, so for example, at a certain point during the life of a deployment, I might want to update my “plugin/themes manifest” and make sure that change is applied to the deployment.

douwe-cmptstks · August 8, 2023, 10:17am

Hi Igor!

To install plugins, you can use the ‘WP_PLUGINLIST’ environment variable which can defined upon creation.

Another thing you can do is utilize the wp cli utility which is included in both the bastion container as the wp container itself.

Here is an example of how the wp users feature works, but running wp cli on the container itself

github.com

ComputeStacks/controller/blob/main/app/services/container_services/wordpress_services/user_service.rb

module ContainerServices::WordpressServices
  class UserService

    attr_accessor :service,
                  :errors

    # @param [Deployment::ContainerService,nil] service
    def initialize(service)
      self.service = service
      self.errors = []
    end

    ##
    # List all admin users
    #
    #     [
    #       {
    #         "ID"=>1,
    #         "user_login"=>"admin",
    #         "display_name"=>"admin",

This file has been truncated. show original

Igor · August 8, 2023, 10:33am

Great, that is precisely what I needed!