Cybélia Forge : your working databases
Completed
Opening a support ticket
175 Views •The vocabulary, in five words
168 Views •Playbooks : ready-made responses
166 Views •Opening my ERP : /open/{db}
163 Views •A database's record : /forge/db/{db}
161 Views •The overview : /dashboard
155 Views •Who it is for
152 Views •My subscription's capabilities : /reglages
151 Views •Both sides before deciding : /bases/rapatrier/comparaison
150 Views •Why this portal exists
148 Views •My changes : /atelier/db/{db}/changes and /changes/scan
145 Views •Help and glossary : /help
143 Views •Creating a test database : /forge/new
143 Views •Your first sign-in : /onboarding
142 Views •My team : /team and /team/add
141 Views •My account : /me, /me/password, /me/locale and /me/mfa
140 Views •The list of my databases : /bases and /bases/fragment
139 Views •Tasks : /atelier/tasks, /atelier/db/{db}/board and /tasks/new
136 Views •Choosing where the copy lands : /bases/rapatrier
134 Views •The go-live : /atelier/db/{db}/production/status
132 Views •Both sides before deciding : /bases/rapatrier/comparaison
The box that fills itself in
This is not a page you open: it is a box that fills after a few seconds inside the "Pull down production" screen. While it loads, a spinner turns with the sentence "We are querying your production to show you both sides".
Why it exists
Replacing your working database is the only destructive action in the portal. You cannot judge whether it is reasonable without knowing what you lose and what you gain. This box answers both questions with real figures, counted since the last pull-down.
What it shows
- What your production has recorded since the last copy: new entries, new documents, the real activity of the company.
- What you have changed in the working database over the same period: your configuration, your experiments, that is, exactly what would disappear.
How to read the two columns: if the "working database" column is empty or nearly so, replace without hesitating. If it holds a week of configuration you have not put live yet, take a copy alongside instead.
If the comparison does not appear
When production cannot be queried at that moment, the box shows the reason in plain words instead of figures. Nothing is blocked: the "copy alongside" path is still available and destroys nothing. That is precisely why the comparison loads separately, the risk-free path should not have to wait for it.
Camille always looks at this box before confirming, even when she already knows what she will choose. It has become her way of checking.
In closing
You do not decide on a destructive action from database names. This panel puts figures on what you lose and what you gain, on both sides, before the button becomes clickable. Take the few seconds it needs to fill in.
Commenting is not enabled on this course.