by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 02 12:01
    derwaldgeist commented #1171
  • Jul 02 11:50
    AfaaqSuhail commented #883
  • Jun 28 19:02
    shiami edited #1179
  • Jun 28 19:02
    shiami edited #1179
  • Jun 28 18:47
    shiami opened #1179
  • Jun 27 22:33
    krizka commented #976
  • Jun 27 13:31
    aeonei closed #1177
  • Jun 27 13:31
    aeonei commented #1177
  • Jun 27 09:08
    ixdi opened #1178
  • Jun 26 05:41
    Bariyard edited #1171
  • Jun 24 22:20
    aeonei opened #1177
  • Jun 22 17:24
    rcsandell edited #1176
  • Jun 22 17:24
    rcsandell opened #1176
  • Jun 22 00:18
    cesarve77 commented #1171
  • Jun 21 09:21
    cesarve77 commented #1171
  • Jun 21 08:40
    Bariyard edited #1171
  • Jun 20 23:13
    PineappleIOnic commented #1171
  • Jun 20 10:44
    Kellokes edited #1175
  • Jun 20 10:43
    Kellokes opened #1175
  • Jun 19 22:12
    SachaG commented #1164
Laurent Roger
@lc3t35
on ec2 instance port 27017
Till
@ruohki
I noticed a strange behaviour. When setting a port in the normal env: { PORT: 3000 } and overriding it in the server: one: env { PORT: 3000 } block mup will expose 3000 on the host and map it to container port 80 BUT the app will be run on port 3000
iam trying to deploy the same application to the same server twice just on different ports and i want to do it in one deploy run
zodern
@zodern
@ruohki If you are using the reverse proxy, that will be fixed in Mup 1.5.
zodern
@zodern
The 10th beta of Mup 1.5 was released today. It is almost ready for a stable release.
Some of the highlights are:
  • Many bug fixes and performance improvements (especially for Prepare Bundle and when deploying to multiple servers)
  • Load balancing and zero downtime deploys
  • Optional swarm integration
  • mup meteor debug command to use a node debugger with your app in production
    More details are in the pull request description: zodern/meteor-up#976
zodern
@zodern

I am working on the plan for Meteor Up 1.6. The focus will be on simplifying creating a plugin, and making sure all plugins are more consistent in features and behavior. Some additional ideas are:

  • Support for marking a server as the bastion/jump host
  • Declarative config to manage firewall
  • More performance improvements
  • meteor shell
  • Add more control and predictability to rolling versions forward/back
  • backup/restore mongo and access to mongo shell
  • Only recreate the reverse proxy container when necessary

I would appreciate feedback on which of these are more or less important ,and if there are any other features that should be considered.

Guillaume Darbonne
@guidouil
@zodern thanks for the great work. I would love more Mongo access and more performance obviously 😁 stay awesome sir 🤟
Laurent Roger
@lc3t35
@zodern thank you ! for me "Add more control and predictability to rolling versions forward/back", maybe you can be inspired by expo.io publish / channel system ?
zodern
@zodern
I released a new plugin to setup Netdata for monitoring servers: https://github.com/zodern/mup-netdata
It is able to setup Netdata with a single master and headless collectors on all other servers. It is very basic, but it should be enough for most use cases.
zodern
@zodern
@lc3t35 I've been considering something like that for a while, but we are a few steps away from it at this point. I haven't found a good solution to what the config or UX should be for that feature since we can't hide the infrastructure like other services with similar features do. Do you have any ideas?
Laurent Roger
@lc3t35
@zodern yes : a releases directory where deploy writes in a channel directory and dated YYYYMMDDHHmm directory, a current link to the current directory in each channel, an id.txt for each deploy (uuid)
mup deploy --channel staging
mup deploy:list -> gives list of id by channel and which one is current
mup deploy:rollback --channel staging --id xxxxx
-> changes the current link in staging to id xxxx
zodern
@zodern

Thanks. I should have been more specific about the difficulties: For some apps the env vars, the servers, or other options should be different between channels/environments. For example, you might not want staging to use the same MONGO_URL as production, or you want production to run on 5 servers, and staging to run on a single, separate server. Right now this is solved by using different mup configs. In the other direction, some options must be the same between environments since the builds will be shared (for example, prepare bundle and build options).

About the implementation, I am planning in Mup 1.6 to version the images created by Prepare Bundle instead of always using latest and previous. Combined with using a private docker registry which will be available in Mup 1.5, this will allow flexibility in what servers are used for what environment/channel.

A feature with some related challenges that I plan to add is support for microservices. The config will probably have an apps array, but I haven't decided what the config should be for plugins that require different configuration per app.
Eric Priou
@erixtekila
Hi all, my deploy command failed at pushing the bundle
Sometimes at 1%, sometimes 15%…
No clue because no logs, eventhough i used DEBUG=mup* mup deploy —verbose
Same issue with DEBUG=mup* mup deploy —verbose --cached-build
Eric Priou
@erixtekila
I use mup@1.4.6
Eric Priou
@erixtekila
Unfortunatly the behavior is similar on mup@1.5.0-beta.11
Eric Priou
@erixtekila
I’m on osx 10.13.6
Eric Priou
@erixtekila
Downgrading nodejs to version 12 soves the issue.
Weliton ferreira
@weliton_sis_twitter
Hello guys
how do I deploy on localhost?
Guillaume Darbonne
@guidouil
That is a strange question. Why would you deploy to localhost?
HUYSIVEING
@huysiveing_gitlab
hello all tgt, can i ask for some question on mup deploy on catalina os not working
anyone help here. coz i can't deploy
Guillaume Darbonne
@guidouil
@huysiveing_gitlab what is the error message? Mup logs?
zodern
@zodern
We will have a new website for Meteor Up 1.5: zodern/meteor-up#1151 The readme has before and after screenshots.
@weliton_sis_twitter I'm curious why you want to deploy to localhost. Mup doesn't support it, but it seems to be a frequent question.
Matt561
@Matt561
I am having the same issue pushing the meteor app bundle to the server. It freezes randomly... sometimes at 0%, 15%, 50%. Not sure what the issue is because there are no logs provided
mup version: 1.4.6, meteor: 1.10.2 meteor node: 12.16.1 imac's node: 14.3.0 (assuming it uses the meteor version)
Laurent Roger
@lc3t35
@Matt561 use DEBUG mode ?
zodern
@zodern
Meteor Up 1.5 has been released. More details are at https://zodern.bearblog.dev/meteor-up-1-5/.
Our new website is also live: http://meteor-up.com/
Erik Demaine
@edemaine
Very exciting progress @zodern! Just gave a quick test, and it's working great (better than all past releases). Looking forward to playing with all the new features!
Micah Alcorn
@micahalcorn
Thanks for continuing to work on this @zodern. 👍
enzo - Eduardo Garcia
@enzolutions
Hi, folks any ideas how to reduce the First Contentful Paint. and the First Meaningful Paint?
Menaker-john
@Menaker-john
Hello everyone, I have what might be a weird question, but is there an easy way to prevent the Nginx config from auto updating when a docker container starts or stops?
zodern
@zodern
It updates whenever containers with certain environment variables are stopped or started. For load balancing to work, we run a light weight container with the env variables: https://github.com/zodern/meteor-up/blob/1b23115728b9f64d9fd05e3ec484858beb0c04f2/src/plugins/proxy/assets/service-configure.sh#L29-L36
That way we can start and stop the app on a server without affecting load balancing.
Artur Sena
@algoz098
Hey!
Im tryng to use mup on aws elastic, over gitlab ci, and having some problems looked into the docs and found nothing about. The commands dies before it should. Someone can help me ?
zodern
@zodern
We should document how to use mup in CI, but there isn't anything special to doing it. Could you please share the logs from running mup? Does it complete any tasks?
Foysal Ahamed
@foysalit
Hope everyone's doing great today. I have this peculiar issue with mup and posted an issue about it on github but may be it will get more exposure here: zodern/meteor-up#1161
what's intriguing is that the app works fine in browser and in the networks tab, I can see that the websocket connection is established without any issue.
Foysal Ahamed
@foysalit
actually nvm, I'm a dummy. I was trying to connect to the server without /websocket suffix.
Elie
@elie222
Any ideas what the ElasticBeanstalk issues are with 1.5?
Reverted to 1.4.6 for now:
zodern/mup-aws-beanstalk#104
Elie
@elie222
Also, would you recommend not using Beanstalk if it isn't properly supported? I really liked that it could massively save us costs. We only a lot of servers running at very specific times so EBS would save us thousands in server costs per year, but have had many headaches since using it
yuwiggin
@yuwiggin
Hi, I have an issue zodern/meteor-up#1166, anyone help?
zodern
@zodern
Version 0.6.4 of mup-aws-beanstalk is now available, which is compatible with mup 1.5.