Nail/fission-src
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update dotnet and perl environment docs for rebuilding env images (#1035)

Browse Source
This commit is contained in:
Ta-Ching Chen
2018-12-23 17:48:09 +08:00
committed by GitHub
parent 3f4eb49c2f
commit ecd99177bb
5 changed files with 18 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files
environments/dotnet/README.md
+5 -42
View File
@@ -35,54 +35,17 @@ Please see examples below.
## Rebuilding and pushing the image ## Rebuilding and pushing the image
To rebuild the image you need either a computer with dotnet 1.1.0 To rebuild the image you will have to install Docker with version higher than 17.05+
installed or else you will have to map the source directory into a in order to support multi-stage builds feature.
container containing the dotnet 1.1.0 environment.
### Locally installed Dotnet 1.1.0 ### Rebuild containers
Simply move to the source directory in a terminal and run the ./build.sh script. Move to the directory containing the source and start the container build process:
The script will restore dependencies, compile a release build and
and build the container. If you need to change the name of the container
simply change it in the script.
After the build finishes push the new image to a Docker registry using the
standard procedure.
### Build in a container
Move to the directory containing the source and start the Docker container
with dotnet and mount the current directory to a build location:
``` ```
docker run -it --rm -v $PWD:/build microsoft/dotnet
```
Move to the build directory inside the container and restore the packages:
```
cd /build
dotnet restore
log : Restoring packages for /source/project.json...
log : Installing System.Net.WebSockets 4.0.0.
log : Installing runtime.native.System.IO.Compression 4.1.0.
...
```
Compile and publish a release build of the source to the 'out' folder:
```
dotnet publish -c Release -o out
Publishing source for .NETCoreApp,Version
...
```
Exit the build container and build the Docker container on the local host:
```
exit
docker build -t USER/dotnet-env . docker build -t USER/dotnet-env .
``` ```
After the build finishes push the new image to a Docker registry using the After the build finishes push the new image to a Docker registry using the
standard procedure. standard procedure.
environments/dotnet/build.sh
-5
View File
@@ -1,5 +0,0 @@
#!/bin/sh
# clean up
rm -rf bin obj out
environments/dotnet20/README.md
+5 -42
View File
@@ -35,54 +35,17 @@ Please see examples below.
## Rebuilding and pushing the image ## Rebuilding and pushing the image
To rebuild the image you need either a computer with dotnet core 2.0.0 To rebuild the image you will have to install Docker with version higher than 17.05+
installed or else you will have to map the source directory into a in order to support multi-stage builds feature.
container containing the dotnet core 2.0.0 environment.
### Locally installed Dotnet core 2.0.0 ### Rebuild containers
Simply move to the source directory in a terminal and run the ./build.sh script. Move to the directory containing the source and start the container build process:
The script will restore dependencies, compile a release build and
and build the container. If you need to change the name of the container
simply change it in the script.
After the build finishes push the new image to a Docker registry using the
standard procedure.
### Build in a container
Move to the directory containing the source and start the Docker container
with dotnet and mount the current directory to a build location:
``` ```
docker run -it --rm -v $PWD:/build microsoft/dotnet
```
Move to the build directory inside the container and restore the packages:
```
cd /build
dotnet restore fission-dotnet20.csproj
log : Restoring packages for /source/project.json...
log : Installing System.Net.WebSockets 4.0.0.
log : Installing runtime.native.System.IO.Compression 4.1.0.
...
```
Compile and publish a release build of the source to the 'out' folder:
```
dotnet publish -c Release -o out
Publishing source for .NETCoreApp,Version
...
```
Exit the build container and build the Docker container on the local host:
```
exit
docker build -t USER/dotnet20-env . docker build -t USER/dotnet20-env .
``` ```
After the build finishes push the new image to a Docker registry using the After the build finishes push the new image to a Docker registry using the
standard procedure. standard procedure.
environments/dotnet20/build.sh
-4
View File
@@ -1,4 +0,0 @@
#!/bin/sh
# clean up
rm -rf bin obj out
environments/perl/README.md
+6
View File
@@ -9,6 +9,12 @@ It is implemented using the lightweight web application framework
Since Twiggy is implemented with [AnyEvent](https://metacpan.org/pod/AnyEvent), Since Twiggy is implemented with [AnyEvent](https://metacpan.org/pod/AnyEvent),
you can write async code using AnyEvent in your function. you can write async code using AnyEvent in your function.
## Build this image
```
docker build -t USER/perl . && docker push USER/perl
```
## Usage ## Usage
The function you upload is actually a perl package returning a coderef (see the The function you upload is actually a perl package returning a coderef (see the