Documentation
Is there a website or WiKi somewhere with a howto or some sort of getting started guide. I'm familiar with Python, but honestly, both Python and CMSynergy are new to me for the most part, so I'm having trouble wrapping my head around this. I'd like to have bidirectional communication (updates going both ways) which I think this will do, but am not sure exactly how. Thanks.
There is no documentation nor wiki available at the moment. I might write a howto soon, but my focus have mostly been on getting to a usable state (which I actually think is reached now).
The converter is not bidirectional, it is only a converter from Synergy -> git.
-A
That's good to know, and still useful to me actually. Any howto would be great though. Thanks for all the efforts. On Feb 14, 2012 4:40 AM, "Aske Olsson" < [email protected]> wrote:
There is no documentation nor wiki available at the moment. I might write a howto soon, but my focus have mostly been on getting to a usable state (which I actually think is reached now).
The converter is not bidirectional, it is only a converter from Synergy -> git.
-A
Reply to this email directly or view it on GitHub: https://github.com/emanuelez/PySynergy/issues/5#issuecomment-3958430
I'll put it higher on the todo list.
Hi,
I did a very short readme some time ago. Is it usable for you? Or should I do more explanations ;)
-Aske
The problem with a UDP joke is that you have no idea if people got it.
On Tue, Feb 14, 2012 at 1:51 PM, buelowp [email protected] wrote:
That's good to know, and still useful to me actually. Any howto would be great though. Thanks for all the efforts. On Feb 14, 2012 4:40 AM, "Aske Olsson" < [email protected]> wrote:
There is no documentation nor wiki available at the moment. I might write a howto soon, but my focus have mostly been on getting to a usable state (which I actually think is reached now).
The converter is not bidirectional, it is only a converter from Synergy -> git.
-A
Reply to this email directly or view it on GitHub: https://github.com/emanuelez/PySynergy/issues/5#issuecomment-3958430
Reply to this email directly or view it on GitHub: https://github.com/emanuelez/PySynergy/issues/5#issuecomment-3960186
On 05/03/2012 08:42 AM, Aske Olsson wrote:
Hi,
I did a very short readme some time ago. Is it usable for you? Or should I do more explanations ;)
-Aske
Yes, I saw that. It's a start. We'll be getting back to this sometime next month. Our project goals shifted a bit, so we're only going one direction now, from git to synergy. We won't be grabbing synergy content until the remote teams start to put that content in synergy, which they haven't done yet.
I appreciate remembering this, and for helpning me out. Thank you.
Pete
Is anyone willing to post their configuration file? I think that could go a long way, I'm having to following each item through the code to figure out what it is for.
My config file anonymized
[synergy] database=/path/to/database base_project=name-version:project:database#1
;Branch project identifiers coma separated heads = name-version:project:database#1
; Master/Mainline project identifier master=name-version:project:database#1
max_sessions=15 ccm_cache_path=/path/to/drive/with/lots/of/space data_file=project-name_hist log_file=synergy_history.log max_recursion_depth=10 skip_binary_files=false
[history conversion] print_graphs=False email_domain=somewhere.com
[ldap] username=username password=pass server=ldap.server.com
Thanks dvaske, i'll give it another try soon.
Hi, I am just trying to convert some of our Synergy Projects to Git. However, you posted that configuration file I can`t figure out what to write at "base_project", "heads" and "master". In Synergy there are no such notations for the branches. Can anyone help me out?
Thanks
The Base project is the Synergy project 4-part-name of the project you want to start the conversion from (initial commit). The heads is a comma separated list of Synergy projects (branches) you want as branches in the new git repo (if any) The master is just the Synergy project you want as the default branch in Git.
Thanks for the quick response! Now I know what I have to put in there.
Well your project/baseline should be of the form: base_project=PROJECTNAME-VERSION:project:DATABASE#1 The same goes for heads and master, but usually with different versions ;)
Conversion is running since yesterday. Do you know whats the issue with big projects? It seems, as if the script doesn`t do anything for quite some time now (exactly 12 hours) because nothing is written in the logfile nor in any other file (but the script is still executed).
It has been a while since I last did any conversion, But first the script extracts all the Synergy data, that usually takes some time as Synergy isn't really that speedy, but I think it should print out some logging information. When all the data is collected, you can run the actual conversion which will build a graph of the different objects and extract their dependency from here.
On Tue, Jan 21, 2014 at 7:36 AM, MeMeMax [email protected] wrote:
Conversion is running since yesterday. Do you know whats the issue with big projects? It seems, as if the script doesn`t do anything for quite some time now (exactly 12 hours) because nothing is written in the logfile nor in any other file (but the script is still executed).
— Reply to this email directly or view it on GitHubhttps://github.com/emanuelez/PySynergy/issues/5#issuecomment-32824818 .
Does anyone know whether the order of the heads, which I have to write into the configuration file, is relevant for a proper dumping in the first script?
It shouldn't be. As I recall it, it just takes them one by one in the order you specify.