Website maintenance

Bee is the command line tool built specifically for Backdrop. It allows you to complete a number of actions on your Backdrop site, and build scripts that automate aspects of site management.

This is an open discussion about Bee; it could be an introduction or we could discuss possible future developments.

Comment below if you would like to talk about anything in particular related to bee.

Triplo has been taking on more support clients, which involves taking care of sites that we didn't originally build. On boarding and managing a roster of support clients while also managing larger development projects poses unique challenges. 

I'd like to share some of the things we're doing at Triplo to grow and support our support offerings and share some of the challenges. 

I'm looking for ideas, tools, workflows, and management techniques that others use to manage their support clients. 

I'm really looking forward to this discussion.

There is a request from an registrant that we discuss: "development workflows (interactions with GitHub, maintain development/user acceptance/production environments)."

Come along to share your experience and learn from others.

During a discussion on bee during the last Backdrop Live, there was discussion around the site alias functionality that drush has, which would enable bee to perform actions on remote installs of Backdrop.  Given that drush support for Backdrop is likely to end with the Drupal 7 End of Life I think that ensuring this functionality is available for bee going forward is becoming more and more important. I would like to explore with people who used the functionality

Let's talk about the "multisite" feature in backdrop and the pros/cons of using that over managing sites individually. 

In this hour I would like to discuss the pros and cons of hosting your site on Pantheon, several strategies for success, and possible future improvements. 

Questions we should address:

1. How many sites/people want to be on Pantheon (but have reservations)?
2. What are the technical challenges for Backdrop sites to be effectively hosted on pantheon?
3. Are there things short of "official support" that Pantheon could do to help?
4. What would "official support" for Backdrop look like?

... that is the question!

This is an intermediate discussion for those who have some experience of managing Backdrop or Drupal with command line tools such as bee, brush and/or drush. It is NOT about command line tools for beginners.

There are three command line tools to support the installation and management of Backdrop websites:

• bee
• brush
• drush (backdrop extension)

Bee, formerly knows as Backdrop Console is inspired by drush and is under active development

Brush, is no longer being maintained in favour of bee

A practical workflow/method to make Upgrading Multiple Sites easy and reliable.

I will have some slides to show my Workflow, then open it up for comments.

I am particularly interested to hear your methods.

A number of people use or want to use Git version control to manage their website between local and hosting servers.  We can discuss the different approaches, challenges with managing git workflows and share ideas for what works and what doesn't.

Which approach do you use?

Are you having issues working out the best way for your situation?

• How to deploy updates?
• How to deploy new features?
• How to deploy config changes?
• How to deploy content changes?