Local Workflow?

Plugins Plugin Development
1

Question for you other plugin devs, what does your local workflow look like?

Right now I have

  1. My source index folder which is tied to git
  2. My plugin in my actual Stash plugins folder

I have to edit the one in my actual plugins folder directly when doing development and then drag the new update into my source index repo.

Is there a way to just have one folder so I don’t have to manually drag and overwrite files all the time?

I tried messing around with the local path of the source index but that didn’t seem to work.

2

manage dev plugins individualy in a “dev” subfolder, once I’m done devving, i delete it and let source index take over, move back if I want to debug

1 Like
3

I dev in prod :stuck_out_tongue:

I have a deploy script that overwrites my plugins assets (not the version files etc), once I’m done i push a release and update to that.

The deploy script also writes a small hash on the page so i know im not on a cached version or whatever.

That way i can be on the same “version” in dev, and updating to the new release works like normal.

The release script does all the updating of the versioning and packaging, hashing etc

4

I’ve finally got Storybook working for plugin development. It’s not perfect, but it’s cut down a large amount of the copy/pasting from my dist folder to dev instance of Stash.

1 Like
5

Second container running stash with dummy data just to test integration. If its solid I do a few days (or hours) of integration tests in prod and catch anything annoying. Pray and push.