However, to answer the main title question you would have to ask @zodern about this one.
Another workaround for this issue is to run mup using node 20.9
1 Like
We haven’t tried Meteor 3 but I know with the beanstalk plugin at least we’ve had to use forks to solve issues. I think poor zodern has too many projects and not enough time. That really is something you’d hope would be maintained by Meteor itself. I know they want to make money from Galaxy but a robust deployment option to the cloud of your choice is vital for Meteor to succeed.
Please tell us more about mio @pmogollon
2 Likes
Sure, www.miawhost.com is the continuation of waveshosting which was abandoned a couple of years ago. We at Propiedata forked it and fixed issues and made some improvements.
It just deploys an app to AWS elastic beanstalk and makes a bit easier to setup and manage than from the AWS console (which i dont like really).
Right now I wont use it for small apps, as the configuration defaults to use a load balancer which would add costs for benefits not required by small projects. Im thinking about adding settings to deploy without the load balancer as I have some small projects that dont require it.
About the planned features, it was something I though might be of interest by the community but it got no traction and I really dont use that much so I just didnt work on it. But if miaw is something people start using ill for sure take a look at the features that will have more impact.
If you want to try it out just register at www.miawhost.com and let me know what you think or if anything is broken you can reach me on discord as paulomogollon.
3 Likes
Can confirm this work around. I’m currently using nodenv to pin the node version used for my meteor projects.
1 Like
Ah, I had forgotten the name. I’m sold straight away on the logo and name 
I’ll make a note to try and check it out when we’re next updating.
Re: load balancers. What would be cool would be to be able to share one between projects so staging, production, test etc can all use the same one. We do that currently to keep costs down. Would MIAW handle it if it’s already setup like that ?
As for gaining traction, I’m not sure. I don’t know how popular a choice EB is here. We really like it and performance is great. Maybe a price/performance comparison with some other setups might drum up some interest ?
ps - your naked domain isn’t redirecting your www subdomain so the links don’t work.
1 Like
@pmogollon I’m seeing a server can’t be found when I click the link.
Thanks for reviving waveshosting. I really liked it back in the day. I’m currently using railway but would definitely consider switching. I think a price/performance comparison like Mark mentioned would be helpful.
jaja it was just for fun at the time I created It and then it stuck with me.
It wont handle the same loadbalancer for multiple envs right now. But ill check it out as it would lower our costs too.
Well, im not sure about the performace side, for me is more about convenience. It just far easier to just deploy a new project and not have to think that much. And then to scale easily and from the go as things move on.
Im adding single instance rn, will check the share of the load balancer also and will fix the domain issue.
Thanks for the feedback.
1 Like
Ill have the price/perf in mind and would probably tackle it after single instances and load balancer sharing.
Thanks.
1 Like
Actually I found that it was not the latest MUP but the node version, MUP currently works only until Node 20.9.0, all newer versions fail.
Remedy with nvm:
$ nvm exec 20.9.0 mup deploy
1 Like
I’m not sure if the problem is in mup or not, but I think mup.js is very important for external deployment.
1 Like
I use MUP, self maintained, from here: GitHub - paulincai/mup-upd. With it I deploy Meteor 3.0.2 with Node 20.15.1. I cannot deploy Meteor 2.15+ and for that I use another self maintained version which is the actual official version with some small NPM updates. I also use a self maintained ‘mup-aws-beanstalk’
3 Likes
@zodern are you still mantaining MUP? or is there anything we can do to help maintaining the project?
MUP is one of the core packages I use with all of my clients projects and would love to have the support for Meteor 3 (with latest node version) + use a mongo db version greater than 5.
1 Like
Sorry for the lack of response. I’ve been traveling for a few weeks and haven’t had much time to follow the discussions or do open source work.
I am still maintaining Meteor Up. Someone had volunteered to submit a PR to fix this issue, but unless I missed it, it hasn’t been done. I’ll publish a new version in a couple weeks when I get home, unless I or someone else finds the time sooner.
The problem is using concurrency when uploading files with sftp. We probably need to update the ssh2 library in both nodemiral and mup. This also requires going through the process of dropping support for Node 8. There is the option of doing a temporary fix of limiting concurrency to 1 in newer node versions, which would make deploys significantly slower.
Regarding mup-aws-beanstalk, its maintenance has always been a little uncertain. The initial version and most of the major improvements (besides the 0.8.0 release) were all sponsored by different individuals or companies. There haven’t been any sponsors in a while. In addition, I also have never had a project where I used it, and developing it is relatively slow, unpleasant, and expensive so it was a lower priority than it probably should have been.
There’s a number of forks with various bugs and features and fixes. I think it would be good if we could centralize the development. If anyone wants to help with this or want to help maintain mup-aws-beanstalk, please let me know.
6 Likes
Looks pretty interesting. Does it support load balancing, hot replacements, and redis-oplog in combination? This is what I was not able to achieve with mup (although I love it in general).
Love to hear that mup is still being maintained. For me, it’s a critical part in my infrastructure. I’m not a DevOps expert, and it helps me a lot to get things up and running. The only thing I am currently missing is that I could not get mup-redis work with mup-beanstalk, so we don’t have hot server updates. I hope mup will still work with Meteor 2 in the forseeable future. Although we eventually will upgrade to Meteor 3, we’re still waiting a bit until the dust has settled down. We’re using quite a number of 3rd party packages.
It uses AWS elastic beanstalk, so it supports load balancers, no downtime deploys, multiple deployment strategies, auto scaling and other options. You will need to use a different server or service for redis. We use AWS elasticache.
4 Likes
A couple of days ago zodern released version 1.5.11 of mup which fixes the above issue. And also an issue I had started having previously with ssh key auth on newer Ubuntu versions.
Just deployed a Meteor 3 project to a Ubuntu 24.04 server and the process went flawlessly.
Added a sponsorship to him as well on github. If you’d like to do so as well, here’s the link: Sponsor @zodern on GitHub Sponsors · GitHub
8 Likes