NEW POTS
Just 4 days until Meteor 3 and Galaxy 2 Launch Week! Let’s talk about Galaxy!
This is not just an update, it’s a significant leap forward, designed to enhance your development experience, and a new logo inspired by the cosmos.
Our new Galaxy logo retains the familiar essence of Meteor, the Galaxy name with a subtle but significant twist.
Join the event and be part of the journey into the new era: Meteor Software - Build with Meteor.js, deploy on Meteor Cloud
Hopefully helpful feedback:
The nouns surrounding the logo represent all the elements of the universe that could remind us about a galaxy (like stars, or a dark hole…) and we use this idea to create a new briefing to the Galaxy logo. In our daily routine, we will use some visual elements in our background art covers (like our article covers, and social art posts).
And the X is a meteor flying by a representation of an elliptical galaxy, kind of like these pictures:
It’s the final countdown! 3 days to go. 
Check out the last video testimonial with @nachocodoner and see the importance of migrating your meteor projects to Meteor 3.
If you haven’t registered yet, now’s the time: Meteor Software - Build with Meteor.js, deploy on Meteor Cloud
Remind you all: the event start at 10:00 AM (GMT-3), you can check your local time here
If you have questions, feedback, or suggestions, ping us on the Slack Community.
What’s the link for the launch week events? I registered but I don’t see the link for some reason.
Hey!
For this first launch, we will make an asynchronous format. The first article is already available here: Embracing the Future: Meteor 3 with Node v20 and Express - DEV Community
In the blog post, it says:
If you are not in version 2.16 yet, make sure to follow the migration guides from your current version up to Meteor 2.16.
Clicking the link brings up a page about migrating to version 2.14. Is there a page about migrating to version 2.16? Or, if I migrate to version 2.14, am I already compatible with version 2.16? I’m currently at version 2.15.
Hey, @vikr00001, version 2.16 is currently a Release Candidate, so there isn’t a migration guide available yet—and there might not be one. We only make migration guides if you need to change something in your app to upgrade or to take advantage of new features or fixes.
You can check out all the links on the Launch Week page: https://meteor.com/meteor-3-galaxy-2-launch. We’re also emailing them to everyone who signed up for launch week updates.
Very good. My app is running in 2.15 - does that mean it’s a good time to start updating to version 3.0?
Okay. Suggestion: change the text in the blog post to:
If you are not in version 2.14 yet, make sure to follow the migration guides from your current version up to Meteor 2.14.
That could avoid confusion.
Meteor 3 and Galaxy 2 Launch Week: Day 3
We’re excited to launch Galaxy Databases, a new addition to our suite of services!
Check out the new article: Unified MeteorJS and MongoDB Hosting.
The missing piece! Congratulations
Do you have any plan for Redis?
We’re excited to launch Galaxy Databases , a new addition to our suite of services. Initially, we’re offering robust support for MongoDB, backed by a dedicated and specialized team ready to assist you every step of the way. But that’s not all – in the near future, we’ll be rolling out support for other databases, including FerretDB, Redis, PostgreSQL , and more. With Galaxy Databases, you can expect top-tier performance, seamless integration, and excellent support for all your data hosting needs.
Meteor 3 and Galaxy 2 Launch Week: Day 4
Yesterday, we finished our Launch Week announcing the transition from Meteor APM to Monti APM! Our goal is to provide our developers with even more powerful tools.
Check out the new article here.
This Week In Meteor
Meteor Dispatches is back with @storyteller, @jkuester and @alimgafar! Today’s episode is about the launch week of Meteor 3 and Galaxy 2! Start in a few moments. Watch here.
Yes, we have plans! And we already provide Redis to customers on custom plans. If you’re looking to use Redis with us right now, you can just contact our support team. It’s just not yet visually integrated with Galaxy.
Awesome! Looking forward to hear more about the Redis option in the future.
I think integrating redis-oplog into the core would further compliment your foothold.
We are discussing this possibility
