Cybélia Forge : your working databases
Completed
The overview : /dashboard
26 Views •My changes : /atelier/db/{db}/changes and /changes/scan
25 Views •Opening my ERP : /open/{db}
25 Views •The vocabulary of Forge
24 Views •My subscription's capabilities : /reglages
23 Views •Both sides before deciding : /bases/rapatrier/comparaison
23 Views •Who it is for
17 Views •Help and glossary : /help
17 Views •Creating a test database : /forge/new
16 Views •Asking for help : /tickets
15 Views •A database's record : /forge/db/{db}
15 Views •The project board : /atelier
15 Views •The project lead and its actions : /atelier/db/{db}, /send, /note, /studio/init, /action/{name}
14 Views •Adopting a copy : /bases/{db}/adopter
14 Views •Choosing where the copy lands : /bases/rapatrier
14 Views •Delete, restore, clear away : /bases/{db}/delete, /restore, /forge/discard/{db}
14 Views •Tasks : /atelier/tasks, /atelier/db/{db}/board and /tasks/new
14 Views •Why this portal exists
14 Views •The go-live : /atelier/db/{db}/production/status
14 Views •The feature catalogue : /playbooks and /playbooks/{feature}
14 Views •Who it is for
Forge does not expect technical knowledge from you. It expects you to know what your trade needs to see on screen. Here are the four people at Les Ateliers du Vent d'Ouest, and what each of them opens.
| Who | What they do in Forge | The screen they open |
|---|---|---|
| Camille management |
Decides what goes live, follows pending requests. | The overview. |
| Marie administration |
Pulls down a fresh copy, checks invoices on that copy. | My databases, Pull down production. |
| Jean workshop |
Tries new screens, notes what is missing, tracks tasks. | The project board. |
| Tom apprentice |
Opens a test database to practise without fear. | My databases, then "Open my ERP". |
Nobody ever works blind. Every database carries its label: working database, test database, copy of production. The screen reminds you where you are before you click.
What if I get it wrong?
A deleted database goes to the bin and can be woken up for 14 days. A failed creation is cleared with one button and leaves nothing behind. A botched experiment on a test database is fixed by deleting it and making another. Only two actions ask you to type a confirmation, and both replace existing content: pulling production into your working database, and deletion.
Tom wiped a price list on his first day. On a test database. Nobody noticed, and he did it again properly that afternoon.
Commenting is not enabled on this course.