Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible to skip the verifying step #9

Open
productiveme opened this issue Feb 23, 2021 · 1 comment
Open

Possible to skip the verifying step #9

productiveme opened this issue Feb 23, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@productiveme
Copy link

productiveme commented Feb 23, 2021

My bot uses DDP connection to connect to RocketChat server and does not expose an endpoint for verification. When I make use of map-node, everything goes well until the verification step when I get

Started app's container
[code.productive.me] - Starting the app: SUCCESS
[code.productive.me] - Verifying Deployment
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to 172.17.0.12 port 3000: Connection refused

Can I somehow bypass the verification?

My mup.js file follows (some details redacted):

module.exports = {
 servers: {
   one: {
     host: '***********',
     username: '***********',
     pem: '***********'
   }
 },

 app: {
   name: 'rocketchat-bot',
   path: '../',
   type: 'node',
   nodeVersion: '15.8.0',

   servers: {
     one: {},
   },

   env: {
     ROCKETCHAT_URL: "https://***********",
     ROCKETCHAT_USER: "***********",
     ROCKETCHAT_ROOM: "***********",
     ROCKETCHAT_USE_SSL: "true",
     ROCKETCHAT_PASSWORD: "***********",
     RESPOND_TO_DM: true,
     PORT: 9000,
   },
   startScript: 'start',
   docker: {
     imagePort: 9000
   },
 },

 plugins: ['mup-node'],
};
@productiveme
Copy link
Author

productiveme commented Feb 23, 2021

I've managed to solve my issue, by looking at the steps generated for the Dockerfile with the DEBUG=mup* mup deploy --verbose and creating my own Dockerfile. This allowed me to publish with mup-docker-deploy plugin instead

@zodern zodern reopened this Feb 23, 2021
@zodern zodern added the enhancement New feature or request label Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants