Frequently asked questions
What is the difference between a Brancher node and a development Hypernode?
A development node is perfect for developing one webshop at a time, running all the single tests you can think of, and giving the customer (the shop owner) access during development. A Brancher node is perfect for testing multiple branches simultaneously without needing to buy multiple dev nodes for at least a month, integration and automation tests without a lingering state at your development node and also giving the customer (shop-owner) access during development.
love Brancher! I might use it as my sole production environment!
Of course, you can do this and nobody is stopping you. But there won’t be backups. Also, the settings you change in the control panel won’t be reflected as well on these nodes. If your use case is production, you need a normal Hypernode. Want advice? We can help.
Do you anonymize the Magento database copied to Brancher with Masquerade?
You can test your software with personal data from your production database if you throw it away when you’re done. But if you still like to anonymize, we do install software like Masquerade on Hypernode by default so you can make this part of your deployment strategy.
I will have to import my anonymised database anyway, so i don't need my database copied to a Brancher at all. Is that also possible?
Yes, this is possible. Simply select “don’t copy the database” when you start a Brancher node.
Why am I being charged without being able to use my Brancher node?
Brancher nodes are designed and conceived with the idea of running short tests. This could, for instance, be testing out a new version of PHP or MySQL. But also, for example, to run a temporary release on a separate brancher node in combination with Deployments. For example, we also use this when we make changes to our support documentation. The change is temporarily run on a Brancher node.
The fact that the timer starts running immediately is indeed intended. We also pay directly for the space reserved with the Cloud Provider.