Question about rollbacks and best practices

  • benjamin.h-1334390020366401547

    Ben H

    9 days ago

    So, in a project, you can see your history with all your previous pushes to production. Next to each one is a rollback button. It looks like if you rollback to a certain time, you lose all of the work that was submitted after that time. For example, if I rollback to the second most recent submission, then I lose the work in the most recent submission. I tested this out in a test project and this does seem to be how it works, though I was a little confused by the "Live Version" indicator. It says the "Live Version" is the one where I added the "test page". But I rolled back to "Deleted blank template", which has no test page, and indeed the test page is gone now. It appears that the "Live Version" simply attaches to the most recent non-rollback update in your history.

    Anyway, I was wondering how rollbacks are best used in practice. If my understanding is correct, it seems like you would almost never use them. You would only ever rollback to the most recent submission (because otherwise you will lose a lot of work) and only in an emergency (because otherwise you would just make a new branch to fix the problem). Is that right? Rather, when rolling out big features, best practice is to add feature flags, and you can "rollback" by turning off the flag. If you implement a big feature with a feature flag but later decide you don't want the feature after all, after turning it off with the flag, you would make a new branch where you delete the feature entirely and publish that new branch to keep your project clean. For smaller features, you would typically just put up with a bug until you can fix it in a new branch, unless it is a game-breaking bug, in which case you would rollback and hope that no one has published a branch lately. Is this a good understanding of how production teams would use toddle in practice?
    1334390020726853632-image.png
  • andreasmoller-1334390566653526038

    Andreas Møller

    9 days ago

    Yes rollback is a panic solution. It is only for when a bug is so servere that you need to undo it right away
    👍1

Stop scrolling. Start building.

toddle is a visual web app builder that rivals custom code — but accessible to your entire team!

Try toddle — it's free!

© Copyright 2024 toddle. All rights reserved.