Plugin dev system setup


3 posts in this topic Last Reply

Recommended Posts

I'd be interested to know other plugin developers dev environment setups?  I struggle constantly making updates in that i have edit the plugin files in place on my server, then copy them down manually to my dev machine to push to git and do the release.  I'd be interested to know if anyone a something easier in place, and even any type of CI/CD integration setup.

Link to post

My work flow


I have /usr/local/emhttp/plugins shared over the network.


I do all development work on a Windows box with the files opened in Network++


When I want to either publish or test out  the plugin on another system, I just issue two commands in my putty session that copies the files back on to the Windows box (which hosts the local GitHub repository), and builds the .txz  On the other servers, I simply installpkg the .txz from the Windows box (the repos are shared over the network)


When I publish, I just change the version of the .plg file and update the md5 listed in the file and push to GitHub.  


Works perfect and painless for me.  And has the upshot that I can directly program on any of the servers and easily build the txz to test the changes on the other ones.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.