<div dir="ltr"><div><div><div><div><div>Thanks a lot all.<br><br></div>I know Drupal is open source, I wanted to protect only the custom modules developed. I learnt from this discussion that - <br><br></div>1. Take a dedicated m/c, so root access is with me. That gives some protection.<br>
</div>2. Will go for a trusted / reputed web hosting company.<br><br></div>On a side note, I read somewhere a separate branch is maintained for Drupal code base (probably 7.4) that is compatible with hihop use., Can somebody give more information in this regard such as is it maintained and available for latest Drupal 7 releases..<br>
<br></div><div>Thanks and Regards<br></div><div>Austin<br></div><div><br></div><div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 25, 2012 at 10:12 PM, Richard Damon <span dir="ltr"><<a href="mailto:Richard@damon-family.org" target="_blank">Richard@damon-family.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/25/12 10:49 AM, Jarry wrote:<br>
> On 25-Dec-12 16:26, Austin Einter wrote:<br>
>> I am worried for few things. Lets say I will be taking a dedicated<br>
>> server say from rackspace or doster or godady and host my site as a<br>
>> commercial one.<br>
>><br>
>> I would not doubt the companies like rackspace or godady ..., but<br>
>> difficult to believe admin engineers who may take the source code and<br>
>> give it to somebody else for few dollars..,<br>
> Source code of what? Drupal or some modules? Drupal is GPL-ed,<br>
> so anybody can have it. Or your own drupal-module? I'm not sure<br>
> but I think if you develop something for Drupal, you have to<br>
> distribute it under the same license at no charge. So which<br>
> php-code you want to obfuscate and why?<br>
><br>
> Jarry<br>
> ---<br>
><br>
</div>The GPL means that *IF* you distribute the results, you need to provide<br>
the source, but there is no requirement to publish source if you do not<br>
distribute your "product" (i.e. for your own use). This is good, as it<br>
means you are not required to publish your settings.php file with your<br>
database passwords!<br>
<br>
This does mean that if you produce as a product a Drupal module, (I<br>
believe) you can not just distribute it as a protected file, you need to<br>
provide the source for it, but this is only if you distribute it.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Richard Damon<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br></div>