Skip to content
Last update: August 24, 2024

Deploy on macOS

Use this guide to deploy and configure precompiled Virto Commerce Platform V3.

Prerequisites

Install LibSass

To install LibSass:

  1. Download the nuget package LibSass Host Native for for OS X (x64).

  2. Unzip the package.

    unzip libsasshost.native.osx-x64.1.x.x.nupkg -d libsass

  3. Move the library to dotnet location path. You can find the location of dotnet using CLI dotnet --info 

    sudo cp libsass/runtimes/osx-x64/native/libsass.dylib /usr/local/share/dotnet/shared/Microsoft.NETCore.App/6.x.x/

Download precomplied binaries

  1. Open the Releases section of the Virto Commerce Platform in GitHub.

  2. Find VirtoCommerce.Platform.3.x.x.zip file. This file contains the prebuilt site and can be executed without additional compilation. The source code is not included.

  3. Download the binaries using the following command:

    wget "https://github.com/VirtoCommerce/vc-platform/releases/download/3.x.x/VirtoCommerce.Platform.3.x.x.zip"

  4. Unpack the downloaded file to the local directory /vc-platform-3 using the following command: 

    unzip VirtoCommerce.Platform.3.x.x.zip -d vc-platform-3

Now you have the directory with the precompiled files of the Virto Commerce Platform.

Setup Platform

To set up the Platform:

  1. Configure application strings.
  2. Run the Platform by CLI "dotnet".
  3. Perform initial sign in.

Configure application strings

To configure application strings:

  1. Open the appsettings.json file in a text editor.

  2. In the ConnectionStrings section, modify the VirtoCommerce node as follows:

        "ConnectionStrings": {
        "VirtoCommerce" : "Data Source={SQL Server URL};Initial Catalog={Database name};Persist Security Info=True;User ID={User name};Password={User password};MultipleActiveResultSets=True;Connect Timeout=30"
    },

    Note

    Make sure the user has permission to create new databases.

  3. To display images, specify the public url for assets by updating Assets:FileSystem:PublicUrl in the Assets section:

    "Assets": {
        "Provider": "FileSystem",
        "FileSystem": {
            "RootPath": "~/assets",
            "PublicUrl": "https://localhost:5001/assets/" <-- Set your platform application url with port localhost:5001
        },
    },

  4. To configure CMS content storage, specify the public url for content for content by updating Content:FileSystem:PublicUrl in the Content section: 

    "Content*": {
        "Provider": "FileSystem",
        "FileSystem": {
            "RootPath": "~/cms-content",
            "PublicUrl": "https://localhost:5001/cms-content/" <-- Set your platform application url with port localhost:5001
        },
    },

  5. Save the appsettings.json file to apply the configurations.

Run Platform by CLI "dotnet"

To run the Platform by CLI:

  1. Install and trust HTTPS certificate. Run steps described in this article to trust the .NET Core SDK HTTPS development certificate on Linux.

    Read more about enforcing HTTPS in ASP.NET Core.

  2. Ensure the Connection String includes ;TrustServerCertificate=True; as shown below:

    appsettings.json
    "ConnectionStrings": {
    "VirtoCommerce": "Data Source=(local);Initial Catalog=VirtoCommerce3.net8;Persist Security Info=True;User ID=virto;Password=virto;Connect Timeout=30;TrustServerCertificate=True;"
},

  3. Run the Platform using the following command:

    export ASPNETCORE_URLS="http://+:5000;https://+:5001"
cd vc-platform-3
dotnet VirtoCommerce.Platform.Web.dll

    Note

    If ports 5000 or 5001 are occupied on your Mac, you can change the port numbers, for example, use 5002 or any other unoccupied port instead of 5000.

  4. The output in the console will be similar to the following:

    Now listening on: http://[::]:5000
Now listening on: https://[::]:5001

Perform initial sign-in

To access the Platform and perform initial sign-in:

  1. Open your browser and type https://localhost:5001.

  2. If you encounter the Your connection is not private error, click Advanced → Proceed to.... This option allows you to proceed to the website even though the browser has detected an issue with the SSL certificate.

    Note

    For additional details on addressing this error and using a self-signed certificate, refer to Trust the ASP.NET Core HTTPS development certificate.

  3. Upon the first request, the application will create and initialize the database.

  4. Once completed, you will be redirected to the sign-in page. Use the following credentials to sign in:

    • Login: admin
    • Password: store

Your Platform is ready to go.