Like you said, you can bootstrap a WebSharper project on a machine with internet access (dotnet new ...., downloading all the required package references, adding custom ones, etc.) and just copy it over to your dev machine. You should be OK unless you have external JS dependencies (probably not to start with, but these would be coming from various WebSharper extensions, for instance), in which case you need to download those as well and redirect the corresponding resource references to point locally.

The current dotnet-based CLI project templates (see the quick start video on the home page) require .NET Core and ASP.NET Core. You can also find older, .NET plain Framework-based templates in the Visual Studio installer from the Downloads page. These include running on Suave/OWIN or a self-hosted server. You can then transfer the resulting binaries/deployment files to your linux host - in theory without any issues.

Hope this helps, cheers.

By on 11/2/2018 9:34 PM ()

The problem I think is that dotnet-based templates don't download NuGet packages in a packages subfolder of the project, but in the user home's .nuget folder. So doing dotnet new elsewhere and copying the folder over won't be enough.

What you can do to remedy this is download the Nuget packages on another computer, but then instead of extracting libraries from it, put them in a folder (say lib) and create a file called NuGet.config with the following contents:

1
2
3
4
5
6

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
</configuration>
This tells NuGet to look for packages in the lib folder rather than from an online source.