zodern on release-1.6
Release 1.6.0-beta.3 (compare)
zodern on release-1.6
Release 1.6.0-beta.2 Merge branch 'release-1.6' of h… (compare)
zodern on release-1.6
Fix Meteor 2.6 compatilibity Release 1.5.6 Fix initializing mongo replica … and 36 more (compare)
zodern on v1.5.8
zodern on master
Release 1.5.8 (compare)
zodern on master
Fix importing uuid (compare)
zodern on master
Release 1.5.8-beta.1 Update uuid (compare)
```Started TaskList: Setup proxy
[46.101.130.237] - Setup Environment
[46.101.130.237] - Setup Environment: SUCCESS
[46.101.130.237] - Pushing the Startup Script
[46.101.130.237] - Pushing the Startup Script: SUCCESS
[46.101.130.237] - Pushing Nginx Config Template
[46.101.130.237] - Pushing Nginx Config Template: SUCCESS
[46.101.130.237] - Pushing Nginx Config
[46.101.130.237] - Pushing Nginx Config: SUCCESS
[46.101.130.237] - Cleaning Up SSL Certificates
[46.101.130.237] - Cleaning Up SSL Certificates: SUCCESS
[46.101.130.237] - Copying SSL Certificate Bundle
[46.101.130.237] - Copying SSL Certificate Bundle: SUCCESS
[46.101.130.237] - Copying SSL Private Key
[46.101.130.237] - Copying SSL Private Key: SUCCESS
[46.101.130.237] - Setup SSL Certificates for Domains
[46.101.130.237] - Setup SSL Certificates for Domains: SUCCESS
[46.101.130.237] - Configure Nginx Upstream
[46.101.130.237] - Configure Nginx Upstream: SUCCESS
Started TaskList: Start proxy
[46.101.130.237] - Start proxy
[46.101.130.237] x Start proxy: FAILED
------------------------------------STDERR------------------------------------
Error response from daemon: endpoint mup-nginx-proxy not found
Error response from daemon: network mup-proxy not found
Error: No such container: mup-nginx-proxy-letsencrypt
Error response from daemon: endpoint mup-nginx-proxy-letsencrypt not found
Error response from daemon: network mup-proxy not found
docker: Error response from daemon: driver failed programming external connectivity on endpoint mup-nginx-proxy (057cfe2e00d4b1ee883bd96e44eee00af88d5afc490dfc4b33bb724954e5a323): Bind for 0.0.0.0:80 failed: port is already allocated.
------------------------------------STDOUT------------------------------------
mup-nginx-proxy
Removed mup-nginx-proxy
Removed mup-nginx-proxy-letsencrypt
latest: Pulling from jrcs/letsencrypt-nginx-proxy-companion
Digest: sha256:c2eaeb6a04620732d30003fecdf9c3ae81c2b7f838fb8485c6f2c21366bffabd
Status: Image is up to date for jrcs/letsencrypt-nginx-proxy-companion:latest
docker.io/jrcs/letsencrypt-nginx-proxy-companion:latest
Using default tag: latest
latest: Pulling from jwilder/nginx-proxy
Digest: sha256:4116f2b6fb9b2a41d94149e8261c81ebbfd96aa84882d87f19c45e00a7c3c221
Status: Image is up to date for jwilder/nginx-proxy:latest
docker.io/jwilder/nginx-proxy:latest
Pulled jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion
d3ecc6eacb03a35e3e49075c957b4fc16f8f42cbb89acecdf00cb331ff20875f
------------------------------------------------------------------------------```
Error response from daemon: Dockerfile parse error line 13: ARG requires exactly one argument
hooks": {
"post.mongo.start" (api)
{
const config = api.getConfig();
console.log(config);
}
}
mup
CLI, or is there an accepted way to do this? I mainly want to keep nginx
up to date without interfering with the normal mup process, so I've been avoiding manually updating the image.
Hi - in need of assistance - been using mup for 4+ years. Love it.
But I'm completely at a loss as to why I'm getting a 503 Service Temporarily Unavailable
. (Am trying to re-release an existing working app to a new Digital Ocean droplet)
mup status
looks like everything has deployed perfectly. Any suggestions?
Meteor version 1.8.2.
image: 'zodern/meteor:root'.
meteor build
(2.2.x) for some reason is generating a bundle/programs/server/package.json
with "source-map-support": "https://github.com/meteor/node-source-map-support/tarball/1912478769d76e5df4c365e147f25896aee6375e"
instead of package version, editing it to "source-map-support": "0.5.20"
workaround the issue.
so you need one token per domain and switch the auth params depending on your url ?
Well when I call Meteor.loginWithGoogle it creates redirect_url to the domain set in ROOT_URL
And looks like it is set here https://github.com/meteor/meteor/blob/4c293d329c9c24acd0c001afad6bcb6d2a4932d0/packages/oauth/oauth_common.js#L3
so you can't redirect to another domain