Hello freek,
First of all, sorry for the late reply.
Silk UI has some static entities, and those will need a really small space on your database (just a few Kb).
However, everytime you publish an eSpace on your environment, you are creating a new version of it, and that version is stored on the database.
So, if you publish 3 times an eSpace that has 5Mb, you will be using 15Mb of database space.
Here is the size of each Silk modules for the latest release of Silk:
Does this answer your question? If not, can you be a bit more specific on your concerns?
Cheers,
Samuel Jesus
First of all, sorry for the late reply.
Silk UI has some static entities, and those will need a really small space on your database (just a few Kb).
However, everytime you publish an eSpace on your environment, you are creating a new version of it, and that version is stored on the database.
So, if you publish 3 times an eSpace that has 5Mb, you will be using 15Mb of database space.
Here is the size of each Silk modules for the latest release of Silk:
- Silk UI Framework - 3.4Mb
- Dublin Template - 1.4Mb
- Liverpool Template - 1.5Mb
- Lisbon Template - 2.3 Mb
- Tokyo Template - 1.3 Mb
- Vanilla Template - 1.1 Mb
Does this answer your question? If not, can you be a bit more specific on your concerns?
Cheers,
Samuel Jesus