Plugin Creation: Difference between revisions
no edit summary
Upazixorys (talk | contribs) No edit summary |
|||
| Line 1: | Line 1: | ||
{| width=90% align=center border=0 style= | =[http://ybyfonojot.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]= | ||
{| width=90% align=center border=0 style="border:3px double black; background: #fee;" | |||
| ''This article is still under editing. Some things still needs to be added and some clarified.'' | | ''This article is still under editing. Some things still needs to be added and some clarified.'' | ||
|} | |} | ||
| Line 30: | Line 31: | ||
== On Board for Plugin Land == | == On Board for Plugin Land == | ||
Now you know the basics but there are still some things I need to make clear off. When making plugins that integrate with the server as one (for example: Resin or Tomcat,) we use the “/usr/local/ | Now you know the basics but there are still some things I need to make clear off. When making plugins that integrate with the server as one (for example: Resin or Tomcat,) we use the “/usr/local/<plugin-name>/” folder. AS you can see how we did the Resin3 plugin, all files pertaining to Resin 3 are kept in the “/usr/local/resin3” folder just as Apache 2 files are kept in “/usr/local/apache2”. This is simplicity. | ||
In version 3.3 we also implemented a new system for the htpasswd files. We made a “/htpasswd” folder for htpasswd file to be kept in. In this directory, all directory are kept in-act. For example, if you have a htpasswd file for a test directory under the “/www” folder, you have to make “/htpasswd/www/test” and place the file under their. This is security and simplicity because it protects the file form the wrong hand since that directory is not viewable or anything by anyone but you. | In version 3.3 we also implemented a new system for the htpasswd files. We made a “/htpasswd” folder for htpasswd file to be kept in. In this directory, all directory are kept in-act. For example, if you have a htpasswd file for a test directory under the “/www” folder, you have to make “/htpasswd/www/test” and place the file under their. This is security and simplicity because it protects the file form the wrong hand since that directory is not viewable or anything by anyone but you. | ||
| Line 39: | Line 40: | ||
A lot of things can be integrated with Apache and we all know that and probably most of you have thought about making that your special small project one day. To try and integrate this with Apache or any other thing the Uniform Server has to offer. Most have actually done it and most are still leaving that at the bottom of the to-do list. | A lot of things can be integrated with Apache and we all know that and probably most of you have thought about making that your special small project one day. To try and integrate this with Apache or any other thing the Uniform Server has to offer. Most have actually done it and most are still leaving that at the bottom of the to-do list. | ||
If you fell you would like to join the user-developer community and really help out, you can. , Search the [http://sourceforge.net/project/showfiles.php?group_id=53691&package_id=49448 Plugin File System] at SourceForge and make sure that none of the plugins you are trying to make is already available, and then send an email to us at [mailto:dev-com@uniformserver.com dev-com@uniformserver.com]. Make sure that the email contains what kind of plugin you are making and some brief info. After that, if you need help or support, you can start a thread in the [http://forum.uniformserver.com/index.php?showforum=12 User Made] sub forum. We would also try and do some study and then get back to you with as much information as we can. | If you fell you would like to join the user-developer community and really help out, you can. , Search the [http://sourceforge.net/project/showfiles.php?group_id=53691&package_id=49448 Plugin File System] at SourceForge and make sure that none of the plugins you are trying to make is already available, and then send an email to us at [mailto:dev-com@uniformserver.com dev-com@uniformserver.com]. Make sure that the email contains what kind of plugin you are making and some brief info. After that, if you need help or support, you can start a thread in the [http://forum.uniformserver.com/index.php?showforum=12 User Made] sub forum. We would also try and do some study and then get back to you with as much information as we can. | ||
If you do not know what kind of plugin you would like to make, you can check the list of feature request in the Feature Request system at SourceForge, do a search on Google, or start a poll or thread in the [http://forum.uniformserver.com/index.php?showforum=14 Open Discussion] forum about what kind of plugins is really needed that is not available. | If you do not know what kind of plugin you would like to make, you can check the list of feature request in the Feature Request system at SourceForge, do a search on Google, or start a poll or thread in the [http://forum.uniformserver.com/index.php?showforum=14 Open Discussion] forum about what kind of plugins is really needed that is not available. | ||
| Line 75: | Line 76: | ||
The READ ME.txt file should follow this format: | The READ ME.txt file should follow this format: | ||
<pre> | |||
---------------------------- | ---------------------------- | ||
PluginName FOR UNISERVER !!! | PluginName FOR UNISERVER !!! | ||
| Line 114: | Line 115: | ||
cannot be held responsible for any type of damage or | cannot be held responsible for any type of damage or | ||
problems caused by using this or another software. | problems caused by using this or another software. | ||
</pre> | |||
You can check other plugins for the format and method used for something. | You can check other plugins for the format and method used for something. | ||