Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FEATURE: Configure the nodeIdentifier of the storage node instead of site and nodePath #24

Open
daniellienert opened this issue Aug 25, 2017 · 0 comments
Open

FEATURE: Configure the nodeIdentifier of the storage node instead of site and nodePath #24

daniellienert opened this issue Aug 25, 2017 · 0 comments

Comments

@daniellienert
Copy link
Contributor

In our use cases, the storage node can be identified by the node identifier.

To use this identifier in the importer has the advantages:

  • The identifier can be found in the backend inspector - no need to look at the database
  • The identifier remains the same, when the node is moved
  • SiteNodePath and storageNodePath can be derived from the node identifier
@daniellienert daniellienert changed the title FEATURE: Configure the nodeIdentifier of the storage node instead on site and nodePath FEATURE: Configure the nodeIdentifier of the storage node instead of site and nodePath Aug 25, 2017
daniellienert added a commit to daniellienert/ContentRepositoryImporter that referenced this issue Aug 25, 2017
@daniellienert
Feature: Define storage node by identifier
909a08b 
Instead of defining the siteNode path and the storage node path,
in case the storage node already exists, you can use the
indetifier of the storage node.

See issue ttreeagency#24
@daniellienert daniellienert mentioned this issue Aug 25, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@daniellienert