URL to SABnzbd ( HTTP included and portnumber where SABnzbd is installed) Usually this requires a portforward but this is outside of the scope of this documentation. When Sabnzbd needs to be accessed through the internet by Spotweb, this requires a setup on your router to make sure Spotweb can reach Sabnzbd directly.
#Where to create group id nzbvortex download
When the user also has the permission to use the Sabnzbd API, it allows the download panel. The NZB file is uploaded to Sabnzbd by Spotweb itself. This option is usually known as ‘push-sabnzbd’, its internal name and as used by the objectid. Now the user is able to select the granted download method using its’ preference screen. Select the checkbox before Use downloads manager API and save it.Go to the Userlist and click on the user you want to give this permission.Use the following as name: Use downloads manager API.Press the + sign at the bottom of this group list.If your chosen download method supports this, please add the following permission to your group. This is a way to check your download progress from another download client within Spotweb itself. Spotweb also supports a ‘download panel’. The ObjectID basically defines which type of NZB handling is allowed for users which are a member of this group.
For the ‘ObjectID’ you enter the value ‘nzbget’ (without quotes). Add the ‘Download manager integration’-permission. Add this group, and click on the pencil icon in the ‘Permissions’-column. Add a new group by clicking on the ‘+’-button.Įnter a new group name – eg: ‘ NZB Handling – NZBGet’. Now open the ‘Admin panel’ and click on the tab ‘Grouplist’. To create a new group, login using a user with administrative permissions – the user ‘admin’ for example. However, we don’t suggest just adding everybody to the administrators group as this will expose your Spotweb installation.įor maximum control, you can create a separate security group for each of the (set of) NZB handling options you want to be able to grant access to. Whether these options are available depends on the permissions a user has, some operations can be ‘dangerous’ to be available for non-trusted users and are prohibited for several users.īy default all users which are a member of the ‘Administrators’ group, have access to all NZB handling options. Really this is a SQL database logic/design question.Spotweb currently suppors the following NZB handling options: The issue here is that I want there to be an unlimited number of groups, and jamming all of a user's group associations into one "value" for each row in my user table seems super sloppy. The other option I could think of would be to create a Group_ID column in the Users table and just fill it with all of the groups a user is associated with in some sort of array of text that would have to be parsed. That option feels like it would create a huge super redundant database table.
I could create a column in the Groups table called "User_ID" and for every group association I have a row that states the Group_ID, the Group_name, and the User_ID. My initial thoughts are to create a Groups table with Group_ID, and Group_name columns. User_ID, User_name, Fname, Lname, is_dealerĭeal_ID, Dealer_ID, Deal_name, Deal_contentĭealer_ID, User_ID, Dealer_name, Dealer address. My current table structure looks like this (Simplified for ease of communication): Users: My question is, what is the best way to handle this user/group association? The group association is going to dictate the priority of contentĮmail updates sent to user will be determined by their current group The users are going to be able to modify their group associations I am going to have an ever growing number of groups and users. I am working on a webapp in PHP/MySQL and I have come to the point where I need to create a user/group association.
0 kommentar(er)
