`forge new project` about forge

[inosik]

Due to the globbing pattern, FAKE tries to build the templates, which get cloned to a sibling directory of the directory, where forge.exe is located (https://github.com/fsharp-editing/Forge/blob/0258550fa0e88f544ddb70b961fdda495b788547/src/Forge.Core/Templates.fs#L113).

So you either have to put Forge to another directory, use the Homebrew formula like described in the README, or we change the target directory, where the templates get cloned to.

[haf]

I can't use the homebrew formula because I'm writing a linux tutorial. So what's the invocation I should perform to have it just work?

[inosik]

For now, I probably would just download and unzip Forge.zip to ~/forge and add that directory to PATH, so that the system can find forge.sh.

[Krzysztof-Cieslak]

Yes, idea is to have "global" / added to PATH installation of forge.

I don't have too much experience with packaging systems for linux so I have no idea what would be good way of providing same deployment for Forge on linux as we currently have for Windows and Mac.

Maybe we should suggest in documentation using something like http://linuxbrew.sh/ and using same brew command as for Mac.

[Krzysztof-Cieslak]

Another thing is way we fail in such case - we clearly should have some better error handling for this case, instead of some random XML exception.

[inosik]

That exception comes from xbuild, I don't know how Forge could react to that, because there is also FAKE involved.

I think the only thing to prevent this, would be not to build the template project files.

[Krzysztof-Cieslak]

Oh, my bad. I think error comes up when user tries to build project (run default ./build.sh provided by Forge) when project was scaffolded in Forge installation directory. It's happening because default build.fsx uses **/*.fsproj glob [so it matches projects in templates folder]

I don't think we can do anything about it. Installing Forge "globally" and running it in solution / repository root of new project should work.