Trevor Lohrbeer

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Trevor Lohrbeer shared this idea  · 
  2. 7 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Service Improvement » Server Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Trevor Lohrbeer commented  · 

    So the hack to not being able to edit .bashrc is to create a .bash_aliases and put your initialization code there.

    It would be more idiomatic though if a separate configuration file was included, since .bash_aliases isn't the appropriate place to modify environment variables.

    Trevor Lohrbeer supported this idea  · 
    Trevor Lohrbeer commented  · 

    Ditto. I'd like to export PS1 to make the prompt tell me which server I'm on.

  3. 3 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Service Improvement » Applications  ·  Flag idea as inappropriate…  ·  Admin →
    Trevor Lohrbeer supported this idea  · 
  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Service Improvement » Applications  ·  Flag idea as inappropriate…  ·  Admin →
    Trevor Lohrbeer supported this idea  · 
    Trevor Lohrbeer commented  · 

    I'll chime in and say that point-in-time restore is not sufficient here.

    Restoring to a point in time is useful if you just want to revert a change. However, if you want to test the Cloudways backup system (which everyone should be doing--trusting that backups just "work" without doing test restores from time-to-time is almost the same as having no backups at all), this doesn't help.

    Also, if you want to test a potential rollback+fix scenario on a test server before deploying that to production, point-in-time restores don't help.

    If you were able to access restore points on cloned applications, that would help solve some of these problems. Then you could clone the application, roll back to a previous restore point on the clone, test different fixes, and then when everything is working, port those changes over to production.

    Alternatively, the ability to download backups and then restore from a local backup through the UI would help achieve a similar aim.

  5. 6 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Service Improvement » Console Improvements  ·  Flag idea as inappropriate…  ·  Admin →
    Trevor Lohrbeer commented  · 

    Agreed. The lack of restore options and documentation on Cloudways is disappointing. Backup is only half of the equation. So far I've been disappointed with the restore options for Cloudways, which include:

    - No option to restore from local backups
    - No option to restore to another server
    - If you clone an application, no option to use the backups from the original application

    Essentially, it makes it extremely difficult to do any sort of testing.

    Trevor Lohrbeer supported this idea  · 

Feedback and Knowledge Base