| Author |
Message |
cyro
Joined: 26 May 2007
Posts: 6
|
 Posted: Fri Oct 24, 2008 2:04 am Post subject: encrypt subversion export |
 |
|
It would be great, when ioncube would act as subversion client. Just submit a repository path, a revision number and a target path and ioncube would encrypt the code directly from svn.
Yeah, this would be realy cool.  |
|
| Back to top |
|
 |
liaison
ionCube Support
Joined: 16 Dec 2004
Posts: 2788
|
| Posted: Fri Oct 24, 2008 8:29 am Post subject: |
|
|
I think that some people are already doing this with the Encoder command line tool and setting up the relevant hooks in SVN.
_________________
Community Admin |
|
| Back to top |
|
|
hontalan
Joined: 23 Sep 2009
Posts: 3
|
| Posted: Wed Sep 23, 2009 1:48 pm Post subject: |
|
|
| nick wrote: | | I think that some people are already doing this with the Encoder command line tool and setting up the relevant hooks in SVN. |
Has anyone successfully set this up? I have been experimenting but my solution isn't the best. Since there is no pre-update hook, the encoding must be done every time there is a commit.
I have set this up successfully in a single-user environment, but with multiple users, different permissions, etc. i run into trouble. Basically my solution is a post-commit svn hook which checks what the latest commit did, and uses that to update a seperate "encoded" version of the source tree.
I will post my solution soon, but it needs some updating...until then, if anyone has any solutions or ideas, lemme know...
_________________
- aron |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
