Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running on CoreCLR #64

Open
tpetricek opened this issue Feb 7, 2016 · 1 comment
Open

Running on CoreCLR #64

tpetricek opened this issue Feb 7, 2016 · 1 comment

Comments

@tpetricek
Copy link
Member

F# Snippets would be a great project to use as a case study for running Suave web applications on Core CLR. It is a fairly straightforward web application that runs nicely on Azure Web Sites currently and uses Azure Storage, but it would be nice to see what a typical Suave web site would need for running smoothly on CoreCLR in a cross-platform environment (say, CoreCLR inside Docker in Azure, still using Azure storage...).

@KevinRansom & community already did some work on porting Suave to run on CoreCLR, so let's open an issue here for this and see what else will be needed!

Once we have CoreCLR version of F# compiler and Suave, the next thing will be integrating it with the new DotNet command line tools so that you can clone the repo and get started with just:

dotnet restore
dotnet run

Thanks to @kunjee17's PR, we now have a neat script that minimizes JS files using some node.js tooling. This involves having Node.js and Npm.js dependencies and then (post-restore, pre-run) invoking them. It looks like DNX had postrestore scripts, which would let us do this nicely, but I'm not sure what is the status - there is a cli issue for this: https://github.com/dotnet/cli/issues/237, but without much information.

@KevinRansom @NumberByColors Do you know if postrestore scripts will be ported to the new dotnet command? Looks like they would be pretty useful for things like running Node as part of your Suave app!

@KevinRansom
Copy link

Keep me in the loop, we need to muck with the build to use the dotnet build tool.

[EDIT by Tomas: Deleted my email to which this is a reply - GitHub was not filtering it properly.]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants