Translations:Arbutus object storage/43/en: Difference between revisions
Jump to navigation
Jump to search
(Importing a new version from external source) |
(Importing a new version from external source) Tag: Manual revert |
||
Line 1: | Line 1: | ||
{{quote|It's important to keep in mind that each data container on the Arbutus Object Store must have a | {{quote|It's important to keep in mind that each data container on the '''Arbutus Object Store''' must have a '''unique name across all users'''. To ensure uniqueness, we may want to prefix our data container names with our project name to avoid conflicts with other users. One useful rule of thumb is to refrain from using generic names like <code>test</code> for data containers. Instead, consider using more specific and unique names like <code>def-myname-test</code>.}} |
Revision as of 16:09, 15 March 2023
It's important to keep in mind that each data container on the Arbutus Object Store must have a unique name across all users. To ensure uniqueness, we may want to prefix our data container names with our project name to avoid conflicts with other users. One useful rule of thumb is to refrain from using generic names like
test
for data containers. Instead, consider using more specific and unique names likedef-myname-test
.