Hi

The config is rather complicated to fill out the node form - In the past you could release from a local to a production and from Production to local (when neeeding to make changes) - I have figured out how to do this - and I gave up to get eisy-ui to do it - it keeps wanting to generate new code

Is there a simple way going between the two - especially from prodution to local - I need to do this for all my nodes that exists already - quite a bit of work

Thanks

@Panda88 ,

I have no idea what you are referring to. It's quite simple:

1. Click on the Development tab

2. Click on the local plugin

3. Click on the Publish button

4. 

there is a lot of info to fill out (that can go wrong). I was hoping to move this info between the two without having to reenter

That's precisely Publish does. It copies all the crucial execution info, but you still need to provide the info that's in production BUT not in local such as Readme, license, and other ...

With kind regards,
Michel

Does it also go the other way - from existing published node to local. Guess this is only an issue during transition to the new system

46 minutes ago, Panda88 said:

Does it also go the other way - from existing published node to local. Guess this is only an issue during transition to the new system

No.

With kind regards,
Michel

Is there a way to setup development nodes using github repositories (not local on machine) - I usually test nodes on multiple systems before releasing, but I do not want development system on more than one eISY. In the past I have created local nodes pointing to the same github branch before releasing it - to allow easy testing - I tried to set the path to github in development, but it does not seem to take it.

@Panda88 ,

I am not sure I understand. github repos are cloned. So, if you have 10 systems pointing to the same repo and use the same path, then you can development on 10 systems.

With kind regards,
Michel

I have one system I use for initial development (nothing critical on that system) - Once a node seems ok, I test on my other critical systems before I release it . With PG3x I just created a node, from the existing released node, and then pointed to my branch/upcoming release and installed that on top of my existing production node. Once ok, I published the local version as a production node.

It is not clear how I can do something similar in the new system - I have not been able to create a development node pointing to github - maybe it is just syntax, but it rejects my attempts on the critical systems.

I do not want to release the node to test it on my other systems - just in case something is not working and it propagates to other systems.

I have been migrating back to PG3x to do this, but it is not a long term solution - furthermore, I have seen a couple of times this results in two versions of the node running in parallel and fighting each other

Edited November 5Nov 5 by Panda88

@Panda88 There are 2 ways you could test your plugin on your production system.

1. Use a local plugin on your production system.

Assuming your development plugin is in a github repository, you can simply clone it on your production unit, install the dependencies, create a local store entry and "install" it. That's the same setup as your development machine. You essentially use github to push the changes from dev, and pull them to your production unit.

2. Use a regular store entry.

On one of your units, create a regular production store entry with a purchase option that points to your github repository, but leave the status to "New" or "Inactive". The plugin will be in the store, but only you (and UDI) will be able to see it.

To install it, Go to Development, My plugins, and click on your plugin. From the Purchase options tab, you will be able to install your plugin. If you want to preview the purchase options as a user, click on "View In Store".

how do i deal with testing an update - not new node?

4 hours ago, Panda88 said:

how do i deal with testing an update - not new node?

Same thing. You have both methods available.

I would recommend the local plugin approach.

I am still not able to create a local plugin that addresses github - it says path not found

I cannot see how the 2nd option works - if I disable the node to test, other users that have it installed (or wanting to install) cannot be served

12 hours ago, Panda88 said:

I am still not able to create a local plugin that addresses github - it says path not found

You can't create a plugin "that addresses github".

You need to clone your repository on your unit. Then the local plugin needs to point to the path on your unit.

12 hours ago, Panda88 said:

I cannot see how the 2nd option works - if I disable the node to test, other users that have it installed (or wanting to install) cannot be served

You would need a second store entry just for that purpose, it would never be published. But this is not the best solution, which is why I recommend the local plugin approach.