Tacomall Documentation

The login page uses uni.login to obtain a WeChat code, which is then sent to the backend via the Member.sendApi method using the wxLogin endpoint.

Workflow:

1. Trigger uni.login to get the code.
2. Call Member.sendApi('wxLogin', ...) with the following payload:
   • params.code: The code from uni.login.
   • params.appid: The MP_APPID from your config.
   • params.invite: An optional invitation string retrieved from page load options.
3. On success (status: true), the response provides a token and an isNew flag.
4. Store the token in localCache using the TOKEN_KEY.
5. Call getMemberInfo() to refresh user data.
6. Redirect the user:
   • If isNew is true: Redirect to /pages/profile/initial/index.
   • If isNew is false: Redirect to /pages/index/index.

Note: The page supports an invite parameter passed via URL/route options during onLoad.

// Conceptual implementation of the login logic
const login = (e) => {
  uni.login({
    success(loginRes) {
      const { code } = loginRes;
      Member.sendApi('wxLogin', {
        params: { 
          code, 
          appid: MP_APPID, 
          invite: invite.value 
        }, 
        body: {}
      }, { errorTip: 'Login failed' }).then(res => {
        const { status, data } = res;
        if (status) {
          const { token, isNew } = data;
          localCache.set(TOKEN_KEY, token);
          getMemberInfo();
          // Navigation logic based on isNew flag
          isNew ? rep('/pages/profile/initial/index') : swi('/pages/index/index');
        }
      });
    }
  });
}

The docker-compose.yml file uses several environment variables to parameterize the service builds, container names, ports, and database configurations. You must define these variables in your environment (e.g., in a .env file) before running docker-compose up.

Core Variables

• PROJECT_NAME: Used as a prefix for all container names (e.g., ${PROJECT_NAME}_mysql).
• IMAGES_ROOT: The base path for building service images and mounting configuration volumes.
• SPRING_PROFILE: Sets the Spring Boot profile for the open, admin, and ma services.

Service-Specific Variables

MySQL

• PORT_MYSQL: The host port mapped to container port 3306.
• MYSQL_ROOT_PASSWORD: The root password for the MySQL instance.
• MYSQL_DATABASE: The name of the initial database to create.

Redis

• PORT_REDIS: The host port mapped to container port 6379.

Nginx

• PORT_NGINX: The host port mapped to container port 80.

Application Services (open, admin, ma)

Each service has a corresponding port variable:

• PORT_OPEN: Mapped to container port 4000.
• PORT_ADMIN: Mapped to container port 4001.
• PORT_MA: Mapped to container port 4002.

The lineChartInit(data) function uses ECharts to render a line chart representing job status trends over time. It targets an HTML element with the ID lineChart.

Chart Configuration:

• Title: Uses I18n.job_dashboard_date_report.
• Legend: Displays statuses for I18n.joblog_status_suc, I18n.joblog_status_fail, and I18n.joblog_status_running.
• X-Axis: Categorical data provided by data.content.triggerDayList.
• Series: Three stacked line series with area styles:
  • Success: data.content.triggerDayCountSucList (Color: #00A65A)
  • Failure: data.content.triggerDayCountFailList (Color: #c23632)
  • Running: data.content.triggerDayCountRunningList (Color: #F39C12)

/**
 * line Chart Init
 */
function lineChartInit(data) {
    // ... configuration object construction ...
    var lineChart = echarts.init(document.getElementById('lineChart'));
    lineChart.setOption(option);
}

The freshChartDate(startDate, endDate) function performs an AJAX POST request to retrieve job dashboard report data for a specific time range. It expects the server to return a JSON object containing chart data. Upon a successful response (code 200), it triggers the initialization of both line and pie charts.

API Endpoint:

• URL: {base_url}/chartInfo
• Method: POST
• Payload Parameters:
  • startDate: Formatted as YYYY-MM-DD HH:mm:ss
  • endDate: Formatted as YYYY-MM-DD HH:mm:ss

Response Structure (Success): The response should include a content object with the following fields used for charting:

• triggerDayList: Array of dates for the X-axis.
• triggerDayCountSucList: Array of success counts for the line chart.
• triggerDayCountFailList: Array of failure counts for the line chart.
• triggerDayCountRunningList: Array of running counts for the line chart.
• triggerCountSucTotal: Total success count for the pie chart.
• triggerCountFailTotal: Total failure count for the pie chart.
• triggerCountRunningTotal: Total running count for the pie chart.

/**
 * fresh Chart Date
 *
 * @param startDate
 * @param endDate
 */
function freshChartDate(startDate, endDate) {
    $.ajax({
        type : 'POST',
        url : base_url + '/chartInfo',
        data : {
            'startDate':startDate.format('YYYY-MM-DD HH:mm:ss'),
            'endDate':endDate.format('YYYY-MM-DD HH:mm:ss')
        },
        dataType : "json",
        success : function(data){
            if (data.code == 200) {
                lineChartInit(data)
                pieChartInit(data);
            } else {
                // Error handling with layer.open
            }
        }
    });
}