Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
File renamed without changes.
File renamed without changes.
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
siyuan:
image: b3log/siyuan:v3.1.17
image: b3log/siyuan:v3.1.18
container_name: ${CONTAINER_NAME}
restart: unless-stopped
ports:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an update to the image field from b3log/siyuan:v3.1.17 to b3log/siyuan:v3.1.18, which suggests that there has been a new release available on Docker Hub for SiYuan. This could be due to bug fixes, feature improvements, or security updates.

Potential Issues: There may not be any known issues with this specific version of SiYuan based solely on its name change. However, it's good practice to review the changelog for both versions to ensure no critical changes were made.

Optimization Suggestions:

  1. Use Tag Constraints: Ensure your Kubernetes manifest (e.g., Deployment.yaml) specifies exact tags instead of using a range (v3.1.*). This allows better control over the image used and can help avoid unexpected behavior during upgrades.

    apiVersion: apps/v1
    kind: Deployment
    metadata:
      labels:
        app: siyuan-svc
      name: siyuan-service
    spec:
      replicas: 1
      strategy:
        type: RollingUpdate
      selector:
        matchLabels:
          app: siyuan-svc
      template:
        metadata:
          labels:
            app: siyuan-svc
        spec:
          containers:
          - image: b3log/siyuan:v3.1.18
            container_name: ${CONTAINER_NAME}
            restartPolicy: UnlessStopped
            ports:
              - containerPort: 6835
                protocol: TCP
  2. Environment Variables: If you need to set environment variables specific to different production environments (Dev/Staging/Production), consider encapsulating them within separate config maps or secrets rather than hardcoding in your deployment files. This improves maintainability and scalability.

  3. Consider Upgrading Dependencies:** Check if there are any compatibility requirements between the updated SiYuan version and other components such as database drivers, plugins, or third-party tools being used in your SIYuan instance. Upgrade dependencies only in cases where they resolve conflicts or improve performance.

  4. Backup Strategy: Ensure you have a robust backup process in place before making significant updates like these. A complete dump of all data plus configuration settings should be stored separately.

By addressing these areas, you can minimize downtime and ensure smooth operation of the SiYuan service after updating to v3.1.18.

Expand Down
File renamed without changes.