Plugin Path

Dev Community Dev/API Corner
1
Add a path during plugin development
Hi forum,

I am still very new to Plex - and I like it more and more! Especially the extendability.

So I decided to start with a Plugin supporting Instagram (I will add it to the appropriate page to let other people know about it soon).

So here's my very first noob question about Plex plugin development: what is your "development best practise" when it comes to editing, testing and committing (Git) the files?


As I have setup a local Git repository I would like to edit the files in the same place as well. But when I want to test the plugin I need to (manually) copy the bundle into ~/Library/Application Support/Plex Media Server/Plug-ins (and yes, I am on a Mac).

Another possibility would be to edit in the Plex plugin directory itself, but then I would need to copy back my changes into my local Git repository (possibly overriding changes I made there in the meantime). Also not very optimal


So what I was searching for is a **possiblity to add a plugin search path to Plex Media Server** such that it would pick up my plugin in the (local) Git repository. That would allow me to edit and test at the same time, and later simply do a "commit".

Googling around I found out about PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR, but that seems 1. only supported on Linux and 2. seems to override the complete plugin path (but I want to *add* a path).

So how do you guys develop your plugins? :)

Thanks,
Oliver
2

Adding a sym-link of your development bundle into the plugin directory allows PMS to pick up the plugin as well as reload it as you make changes. On the command line, you can create a sym-link by executing:


ln -s <path to your dev bundle> <path to plugin directory/your plugin bundle>


I know that for OSX there's also a program which can add the option to create sym-links to the Finder's right-click context menu. I don't remember what it's called offhand.
3


Ha! Easy and effective! Works like a charm - wouldn't have occured to my mind though ;) Thanks a lot!

Oh and I am familiar with Terminal, don't worry ;)

Cheers, Oliver
4

I look forward to seeing what you’re cooking up :slight_smile:

5


It's going to be Instagram support. I just managed to get the OAuth 2.0 authorisation working - without the need to display anything in a web browser or have the user input the OAuth token! So an important milestone has been reached ;)
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.