zodern / meteor-up

Production Quality Meteor Deployment to Anywhere
http://meteor-up.com/
MIT License
1.27k stars 281 forks source link

mup does not deploy latest code #1251

Open Josh-of-TT opened 3 years ago

Josh-of-TT commented 3 years ago

Mup version: 1.5.3

Mup config

{
  "servers": {
    "one": {
      "host": "1.2.3.4",
      "username": "root",
      "opts": {
        "port": 22
      }
    }
  },
  "app": {
    "name": "my-app",
    "path": "/Users/my-name/Sites/my-app/",
    "servers": {
      "one": {}
    },
    "buildOptions": {
      "serverOnly": true
    },
    "env": {
      "ROOT_URL": "https://subdomain.host.com",
      "MONGO_URL": "mongodb://mongodb:27017/my-app",
      "MONGO_OPLOG_URL": "mongodb://mongodb/local",
      "VIRTUAL_HOST": "subdomain.host.com",
      "HTTPS_METHOD": "redirect",
      "LETSENCRYPT_HOST": "subdomain.host.com",
      "LETSENCRYPT_EMAIL": "email@domain.com",
      "VIRTUAL_PORT": 3000,
      "HTTP_FORWARDED_COUNT": 1
    },
    "docker": {
      "image": "abernix/meteord:node-12-base",
      "prepareBundle": true,
      "useBuildKit": true,
      "stopAppDuringPrepareBundle": false,
      "imagePort": 3000,
      "args": [
        "--link=mongodb:mongodb"
      ]
    },
    "type": "meteor"
  },
  "mongo": {
    "version": "4.2.8",
    "servers": {
      "one": {}
    },
    "dbName": "app"
  },
  "proxy": {
    "domains": "subdomain.host.com",
    "ssl": {
      "letsEncryptEmail": "email@domain.com",
      "forceSSL": true
    }
  }
}
✓ Config is valid

Output of command

⚡︎mup deploy --verbose --servers=https:/my.site.com --settings=settings.json                                                ∞
Building App Bundle Locally
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating

Started TaskList: Pushing Meteor App

Started TaskList: Configuring App

Started TaskList: Start Meteor

Note: settings.json only holds our encryption key to securely encrypt user data

We host with Digital Ocean, and my issue is that every time I attempt to deploy our latest code, it seems as if mup is stuck around a month ago. I can not get our latest code to deploy.

Running locally I am seeing all the latest code/features.

Josh-of-TT commented 3 years ago

Error log from today:

Building App Bundle Locally
Errors prevented bundling:
While building for web.browser:
packages/blaze-hot/hot.js: [BABEL] /Users/.../packages/blaze-hot/hot.js: React Refresh Babel transform should only be enabled in development environment. Instead, the
environment is: "production". If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
packages/blaze-hot/update-templates.js: [BABEL] /Users/.../packages/blaze-hot/update-templates.js: React Refresh Babel transform should only be enabled in development
environment. Instead, the environment is: "production". If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/app-animations.js: [BABEL] /Users/.../client/app-animations.js: React Refresh Babel transform should only be enabled in development environment. Instead, the
environment is: "production". If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/body.js: [BABEL] /Users/.../client/body.js: React Refresh Babel transform should only be enabled in development environment. Instead, the environment is: "production".
If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/global-functions.js: [BABEL] /Users/.../client/global-functions.js: React Refresh Babel transform should only be enabled in development environment. Instead, the
environment is: "production". If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/global-helpers.js: [BABEL] /Users/.../client/global-helpers.js: React Refresh Babel transform should only be enabled in development environment. Instead, the
environment is: "production". If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/nav.js: [BABEL] /Users/.../client/nav.js: React Refresh Babel transform should only be enabled in development environment. Instead, the environment is: "production".
If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
client/main.js: [BABEL] /Users/.../client/main.js: React Refresh Babel transform should only be enabled in development environment. Instead, the environment is: "production".
If you want to override this check, pass {skipEnvCheck: true} as plugin options. (While processing: "base$0$0")
wzard commented 3 years ago

Facing the same issue. Were you able to resolve @Josh-of-TT ?

eugle commented 2 years ago

Facing the same issue.

eugle commented 2 years ago

Magic question, delete buildoptions > debug: true, it succeeded, my God

buildOptions: {
            serverOnly: true,
            //debug: true,  //Delete this 
            allowIncompatibleUpdates: true
        },
Josh-of-TT commented 1 month ago

apologies - I did not receive a notice of your replys - we moved to a different deploy pattern.