How to build Squidex using Docker or manually.
squidex/squidex:latestis the latest stable version.
squidex/squidex:vX.XXis a specific stable version.
squidex/squidex:devis the latest dev version (master branch).
squidex/squidex:dex-XXXXis a specific dev version (master branch).
To build a custom image use the multistage Dockerfile. Just run:
docker build . -t my/squidex
When you want to deploy to IIS or NGINX you might want to build it manually. Note that we also provide the prebuild binaries on Github, link below.
You can then find the files under
Run the following commands in PowerShell or bash to build Squidex with docker:
# Build the image
docker build . -t squidex-build-image -f dockerfile.build
# Open the image
docker create --name squidex-build-container squidex-build-image
# Copy the output to the host file system
docker cp squidex-build-container:/out ./publish
docker rm squidex-build-container
In Windows, just use the
If you don't want to use docker, you can also build it manually. The project structure has changed slightly its migration from .NET Core 2.X to .NET Core 3.0.
The new structure differentiates between the frontend and the backend.
This has the advantage that the code is separated and we can use multiple contains to build them independently, making better use of caching in docker. After both frontend and backend, have been built, you need to copy the build artifacts to a common folder. We just assume that we use
To build the backend, run the following commands.
dotnet publish --configuration Release --output "../../../publish"
To build the frontend, run the following commands.
npm i # Install npm packages
npm run build
copy build "../publish/wwwroot/build"
npm run build
dotnet publish --configuration Release --output "../../publish"
Please note that, on Windows you have to run PowerShell or CMD.exe in elevated mode (run as Administrator) to install all required build tools for node-sass.
npm install --global --production windows-build-tools