MadCap Software Forums

Hi there,

I'm completely new to Madcap Flare and setting up a test project. Subversion checkouts here use the form http://svn/svn/.... From that I made an assumption about the value for server.

In the Bind Project dialog I specified the following:

• Server: svn://svn
• Project Path: http://svn/svn/docsvn/Test

However I just get the following errors:



Any help for correct values appreciated.

P.

You need the full URL to the server, and you've entered only part of it, apparently. I'd ask the server administrator what the full path is, instead of making an assumption.

Hi Nita,

Talking to the engineer in charge of Subversion here, it turns out the repository isn't accessible via svn protocol for security reasons, only HTTP.

P.

I am not sure how realistic your URL example is, but in my environment, I cannot omit the www or the .com.

We use URLs, rather than SVN addresses.

servobot wrote:I am not sure how realistic your URL example is, but in my environment, I cannot omit the www or the .com.

We use URLs, rather than SVN addresses.

The URL shown works within our environment anyway ("svn" resolves locally)

In the Server field I tried using http:// instead of svn://, but instead I get the error "Bind failed; login failed for server". (At this point should I be prompted for a username and password to use for the server?)

P.

I think that users' experiences are going to vary depending on their particular setup. I would think the server administrator can help you sort this out. If he or she can't help, you might need MadCap support to help sort it out.

Maybe my old post can help out here: http://forums.madcapsoftware.com/viewto ... 02&p=72291

Oceanclub,
Does your company use Visual SVN? If you can get the url to the visual SVN server, it is the same URL that Flare needs. Does your url need a port number? My svn server is on port 8443, so my url looks like:

https://[server name]:8443/[folder names]

Hi Chris,

No port number is needed. For example, using TortoiseSVN, here's the URL I would use to access a test directory I've created:

http://proddev-svn/svn/docsvn/Test/

The above works fine with TortoiseSVN. However, none of the following combinations work with Flare:

Server: http://proddev-svn
Project Path: http://proddev-svn/svn/docsvn/Test/

Server: proddev-svn
Project Path: http://proddev-svn/svn/docsvn/Test/

Server: svn://proddev-svn
Project Path: http://proddev-svn/svn/docsvn/Test/

The example tip below the Server field uses the svn protocol - does the value _have_ to use svn? If so then I can't use Flare with Subversion as this protocol is locked down for security reasons.

P.

oceanclub wrote:The example tip below the Server field uses the svn protocol - does the value _have_ to use svn? If so then I can't use Flare with Subversion as this protocol is locked down for security reasons.

Not in my experience. For one of my clients' work, the protocol is https, for another it's svn+ssh, and I once set up a test server for which I used file. In at least the first two cases (I can't recall for the third), there is user authentication. For example, for the svn+ssh protocol (for which, BTW, I had to edit the server config file to include a tunnel command, as instructed by the server admin), before I start up a Flare project, I use Pageant to load a private key file (provided by the server admin) before Flare can access the server.

Have you found that your server admin has no advice to offer?

I place the entire path to the project in the server field, and I use https.

My path looks like this:
Server: https://[server name]/svn/[top level folder name]

When I click the browse button I choose the folder with the $ to place my project at the root of my top level folder.

Flare and/or SVN will not let me browse or add projects at the https://[server name]/svn level.

In your examples, your server path always stops at svn. That doesn't work for me when I attempt it. Try to use one more folder below svn.

ChrisBradley wrote:I place the entire path to the project in the server field, and I use https.

My path looks like this:
Server: https://[server name]/svn/[top level folder name]

When I click the browse button I choose the folder with the $ to place my project at the root of my top level folder.

Flare and/or SVN will not let me browse or add projects at the https://[server name]/svn level.

In your examples, your server path always stops at svn. That doesn't work for me when I attempt it. Try to use one more folder below svn.

Hi Chris,

Many thanks for this info - didn't reply sooner as I was busy with other work and didn't get to test it til now. Your format did indeed work for me:

Server: LIke you, I found I had to use https even though I normally use http. Also, giving just the server name wasn't sufficient - I had to give the server name plus the highest folder to which I had access. So, in our case it was https://{server}/svn/docsvn/.

Project Path: Once the above was specified, this was easy, simply http://{server}/svn/docsvn/Test/Installation Guide (note http rather than https in this case).

So, just to sum up, in our case, use https rather than svn, and specify not just the server name but include a whole path to the highest level to which you have access.

P.

Glad it worked out!