This topic describes how to deploy a Whatsns application to Function Compute. Function Compute provides a method different from traditional deployment methods. You can deploy a traditional Whatsns application to Function Compute and use the application for production without performing operations such as purchasing a server. The deployed Whatsns application can use the auto scaling, pay-as-you-go, and O&M-free features of Function Compute.


The following operations are complete:


  1. Run the following command in the specified directory to initialize a project:
    s init devsapp/start-whatsns -d start-whatsns
    The -d parameter specifies the project name. In this example, the project name is start-whatsns.
    Note Skip this step if the item exists.
    Sample command output:
     Serverless Awesome:
     devsapp! file decompression completed
     please select credential alias default
         _    _ _           _   _____ _   _  _____
        | |  | | |         | | /  ___| \ | |/  ___|
        | |  | | |__   __ _| |_\ `--.|  \| |\ `--.
        | |/\| | '_ \ / _` | __|`--. \ . ` | `--. \
        \  /\  / | | | (_| | |_/\__/ / |\  |/\__/ /
         \/  \/|_| |_|\__,_|\__\____/\_| \_/\____/
        Welcome to the start-whatsns application
         This application requires to open these services:
             FC :
         This application can help you quickly deploy the Whatsns project:
             Full yaml configuration:
             Whatsns development docs:
         This application homepage:
     Thanks for using Serverless-Devs
     You could [cd /test/start-django/start-whatsns] and enjoy your serverless journey!
     If you need help for this example, you can use [s -h] after you enter folder.
     Document Star:
  2. Run the following command to go to the project directory:
    cd start-whatsns
  3. Run the following command to deploy the project:
    s deploy
    Sample command output:
    [2021-09-01T11:07:30.473] [INFO ] [S-CLI] - Start ...
      devsapp! file decompression completed
     Using web framework type: nas, If you want to deploy with container, you can [s cli fc-default set web-framework container] to switch.
    (node:2456) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
    (Use `node --trace-deprecation ...` to show where the warning was created)
      End of request
      End of request
    [2021-09-01T11:07:53.743] [INFO ] [FC-DEPLOY] - Using region: cn-shenzhen
    [2021-09-01T11:07:53.745] [INFO ] [FC-DEPLOY] - Using access alias: default
    [2021-09-01T11:07:53.745] [INFO ] [FC-DEPLOY] - Using accessKeyID: 188077086902****
    [2021-09-01T11:07:53.745] [INFO ] [FC-DEPLOY] - Using accessKeySecret: KdcUEJLoGto****
     Using fc deploy type: sdk, If you want to deploy with pulumi, you can [s cli fc-default set deploy-type pulumi] to switch.
    [2021-09-01T11:07:54.340] [INFO ] [FC-DEPLOY] - Checking Service serverless-devs-whatsns exists
    [2021-09-01T11:07:55.012] [INFO ] [FC-DEPLOY] - Setting role: AliyunFCDefaultRole
    [2021-09-01T11:07:55.294] [INFO ] [RAM] - Checking Role AliyunFCDefaultRole exists
    [2021-09-01T11:07:55.468] [INFO ] [RAM] - Updating role: AliyunFCDefaultRole
    [2021-09-01T11:07:55.556] [INFO ] [RAM] - Checking Plicy AliyunFCDefaultRolePolicy exists
    [2021-09-01T11:07:55.686] [INFO ] [FC-DEPLOY] - Using vpcConfig: auto: fc will try to generate related vpc resources automatically
    [2021-09-01T11:07:56.422] [INFO ] [VPC] - Getting vpc: fc-deploy-component-generated-vpc-cn-shenzhen
    [2021-09-01T11:07:56.512] [INFO ] [VPC] - Getting vswitch: fc-deploy-component-generated-vswitch-cn-shenzhen
    [2021-09-01T11:07:56.642] [INFO ] [VPC] - Getting securityGroup: fc-deploy-component-generated-securityGroup-cn-shenzhen
    [2021-09-01T11:07:56.827] [INFO ] [FC-DEPLOY] - Generated vpcConfig:
    securityGroupId: sg-wz92ctigpi221smc****
    vSwitchId: vsw-wz9qnuult4q5g4f7n****
    vpcId: vpc-wz9x9bzs0wtvjgt6n****
    [2021-09-01T11:07:56.827] [INFO ] [FC-DEPLOY] - Using nasConfig: auto: fc will try to generate related nas file system automatically
    [2021-09-01T11:08:22.851] [INFO ] [FC-DEPLOY] - Generated nasConfig:
    groupId: 10003
      - fcDir: /mnt/auto
        nasDir: /serverless-devs-whatsns
    userId: 10003
    [2021-09-01T11:08:22.854] [INFO ] [FC-DEPLOY] - Checking Function whatsns exists
    [2021-09-01T11:08:22.998] [WARN ] [FC-DEPLOY] - Image dose not exist locally.
    Maybe you need to run 's build' first if it dose not exist remotely.
    [2021-09-01T11:08:23.002] [INFO ] [FC-DEPLOY] - Checking Trigger serverless-devs-whatsns exists
    [2021-09-01T11:08:23.097] [INFO ] [FC-DEPLOY] - Checking Trigger serverless-devs-whatsns exists
    [2021-09-01T11:08:23.213] [INFO ] [FC-DEPLOY] - Creating service: serverless-devs-whatsns
    [2021-09-01T11:08:23.213] [INFO ] [FC-DEPLOY] - Creating function: whatsns
    [2021-09-01T11:08:23.214] [INFO ] [FC-DEPLOY] - Creating triggers: ["serverless-devs-whatsns"]
      Make service serverless-devs-whatsns success.
      Make function serverless-devs-whatsns/whatsns success.
      Make trigger serverless-devs-whatsns/whatsns/serverless-devs-whatsns success.
    [2021-09-01T11:08:26.167] [INFO ] [FC-DEPLOY] - Checking Service serverless-devs-whatsns exists
    [2021-09-01T11:08:26.240] [INFO ] [FC-DEPLOY] - Checking Function whatsns exists
    [2021-09-01T11:08:26.389] [INFO ] [FC-DEPLOY] - Checking Trigger serverless-devs-whatsns exists
    [2021-09-01T11:08:26.594] [INFO ] [FC-DEPLOY] - Creating custom domain: whatsns.serverless-devs-whatsns.188077086902****
    [2021-09-01T11:08:27.301] [INFO ] [FC-DOMAIN] - Creating custom domain: whatsns.serverless-devs-whatsns.188077086902****
    There is auto config in the service: serverless-devs-whatsns
    [2021-09-01T11:08:28.256] [INFO ] [WEB-FRAMEWORK] - nas component get src is: ./code
    Packing ...
    Package complete.
     Start uploading file: /mnt/2bfb748534-tpm20-cn-shenzhen/serverless-devs-whatsns/whatsns/
      File uploaded successfully: /mnt/2bfb748534-tpm20-cn-shenzhen/serverless-devs-whatsns/whatsns/
      upload done
    [2021-09-01T11:11:26.451] [INFO ] [FC-NAS] - unzipping file
    [2021-09-01T11:11:37.836] [INFO ] [FC-NAS] - unzip done
      Try container acceleration
      region: cn-shenzhen
      serviceName: serverless-devs-whatsns
      functionName: whatsns
        - >-


After the project is deployed, you can view the temporary domain name generated by Function Compute in the execution output. The temporary domain name can be used to access the newly deployed application. For example, run the following command to access the application:

curl http://whatsns.serverless-devs-whatsns.188077086902****
Note The temporary domain name is used only for demonstration and development purposes. It is valid for a limited period of time. You must use a domain name that has obtained an Internet Content Provider (ICP) filing from Alibaba Cloud for production. For more information, see Configure a custom domain name.