Re: tough question - good luck :)

[Joe C. <jo...@sw...>]

Have a look in the module.info file in the module directory.  After 
copying the module directory to a new dir name (i.e. apache becomes 
myapache), modify the module.info to contain a new name (Apache becomes 
MyApache, for instance).

I think that will do it.  From now on, you can update Apache alongside 
the rest of Webmin, and your MyApache module will remain the same.

Terry Davis wrote:

> Ok, but what if I wanted to create a whole new module out of it?  Is 
> this possible?
> 
> Jamie Cameron wrote:
> 
>> Terry Davis wrote:
>>
>>> I have made some changes to the code that I dont want to lose when I
>>> update.  Is there a way I can export that module in its current state
>>> and rename it to a different module?  THat way, when I update, the main
>>> module can be updated while my "exported" module remains the same.
>>>
>>> Thank you!
>>> Hope this makes sense.
>>>
>>
>> Your best option would be to copy the module directory to a new name,
>> (making sure to copy /etc/webmin/modulename as well) and then grant 
>> yourself
>> access to the copy rather than to the original. That way when webmin 
>> is upgraded
>> it will leave the copy alone and only upgrade the original directory ..
>>
>>   - Jamie
>>
> 
> 
> 



-- 
Joe Cooper <jo...@sw...>
http://www.swelltech.com
Web Caching Appliances and Support