mirror of
https://github.com/node-red/node-red.git
synced 2023-10-10 13:36:53 +02:00
Updated Design: Version Control (markdown)
parent
3f5b15e7c2
commit
e256bea61e
@ -7,6 +7,8 @@ When we talk about version control of node-red instances, there are two things t
|
|||||||
|
|
||||||
It is desirable to have a single artefact (or logical set of artefacts) that can be maintained in version control and used to restore a system to a previous known state.
|
It is desirable to have a single artefact (or logical set of artefacts) that can be maintained in version control and used to restore a system to a previous known state.
|
||||||
|
|
||||||
|
The priority is version control of flows/credentials - and is the main focus of this work. The *Added Nodes* scenarios are for a future piece of work.
|
||||||
|
|
||||||
### Added Nodes
|
### Added Nodes
|
||||||
|
|
||||||
Currently, a user simply npm installs nodes in their user directory to add them to the runtime - or uses the admin api to do so. There is no requirement to maintain a `package.json` file. But it is that file that needs to be version controlled in order to have a restorable system.
|
Currently, a user simply npm installs nodes in their user directory to add them to the runtime - or uses the admin api to do so. There is no requirement to maintain a `package.json` file. But it is that file that needs to be version controlled in order to have a restorable system.
|
||||||
|
Loading…
Reference in New Issue
Block a user