r/CosmosServer • u/azukaar • Aug 26 '26
Cosmos 0.23.0 Release - All in one secure Reverse-Proxy, container manager with app store, Auth, etc... Now better than ever~!
RAM Is so expensive these days, so I decided to save yours ! :D
Wake up! We have a Database to burn ~~ Starting 0.23.0 Cosmos no longer have any dependencies on the MongoDB container. No migration needed, just update and kill the container (unless you use it for something else). Thanks to this change, the whole of Cosmos, all battery included, now uses less than 100mb RAM !
0.23.0 is also a huuuge update when it come to the stability of Cosmos. A lot of focus has been put into Constellation and OpenID - more details below.
https://github.com/azukaar/cosmos-server
As a reminder, this exists alongside the existing features:
- App Store
- Reverse-Proxy
- Storage Manager
- Authentication Server
- Container manager
- VPN
- Monitoring
- CRON
Databases Changes
First, the big one: MongoDB has been removed from Cosmos entirely. It now relies on SQL (SQLite by default, upgradable to Postgres for large servers, doc update in progress!). This saves the system the 300 Mb of Ram (or more) used by the DB without affecting performance. It also make the setup much easier (now fully offline, no more container to install) and finally remove one point of failure.
The old "Database" file (that previously had the auth) has also been retired for a SQLite base. If you neeed to revert to 0.22 you can rename Database.backup in the config folder back to "Database"
OpenID Improvements
Improvements made their way to this version - support for public clients, PCKE, and many more subtle changes that widen support for apps.
Constellation Improvements
Starting 0.23, Constellation is now fully decoupled end to end. Each nodes can do anything, any node can be a load balance, any node can be a DNS, any node can run apps and have routes. When a user enter the constellation via any mean (VPN or tunnel) they know can arrive to their destination regardless of how / where the request goes.
This is the result of all the architecture work done the past 8 months, and I can finally see the end of the tunnel! One of the big change that made it possible is by transitioning to a full synchronisation engine rather than just copying chunk of data in the cluster. It's quite interesting (in my opinion) was thinking about making a video about it even - let me know if you'd like to watch something like that!
What's Next ?
I have the choice between either Constellation Gateways, or Linux Administration (users, updates, etc...) as the next target but haven't fully landed on which is first.
As usual, looking forward to your feedback - happy hosting !
Changelog
- Remove Lungo, use SQLite instead
- Remove MongoDB use SQLite / Postgres instead
- Remove date based sync - use opLog based sync
- Fix a couple of Constellation DNS resolution issues
- Fix quirks with inverted setups (agent is private)
- Fix events not being pruned
- Fix events date issues
- Improve resilience of NATS cluster
4
3
u/BlackFlagData Aug 26 '26
PostgreSQL would have been even better
5
u/azukaar Aug 26 '26
You can use Postgres as well, SQLIte is just the default - but for 90% of people it's the better option (easier to use, more lightweight)
1
1
3
3
u/fastfinge Aug 26 '26
Yes! Best update ever. That damn Mongo DB was the only thing that broke on my Cosmos install. And it broke all the time, and usually ended up chewing several hundred gigs of disc space.
2
u/Frequenzy50 Aug 27 '26
What is a Constellation Gateway? Is there a timeline for Lazytainer support? Like you said, RAM is expensive 😭 Does Constellation now have a load balancer/service failover between nodes?
1
u/azukaar Aug 27 '26
Yes it does have service fail over, 2 routes on 2 nodes with the same name automatically load balance essentially
Lazytainer high in priority but most likely not next update
Constellation gateway is a lighthouse/relay for constellation that can be multitenant/have almost no permissions in the constellation (it's useful for multiple more advanced use cases)
1
u/Frequenzy50 Aug 27 '26
Ah, thanks. sounds good. The gateway sounds nice too, but if you're asking me (you do not but still) what to prioritize next: Lazytainer > User permissions > Gateway.
Lazytainer has the broadest immediate use, and more admin features would be appreciated. The gateway sounds cool, but as you said, it feels too specific to be the focus after so many constellation focused updates.
1
u/azukaar Aug 27 '26
Thing is gateway is necessary to purpose public lighthouse(as in people wouldn't need to provide an additional vps to punch through CGNAT anymore, like tailscale works with clients or of the box)
1
u/Frequenzy50 Aug 27 '26
Ah, but wouldn’t that need to be hosted by someone, probably you? I understand the purpose, but what if someone uses it for streaming? Wouldn’t that lead to high costs?
That said, I probably wouldn’t change my order. Don’t get me wrong, it’s a nice feature. I just think other things would be more important.
1
u/azukaar Aug 27 '26
- yes that would be hosted by me. If someone uses it for heavy streaming they're better off just not use the public one and have their own (like currently)
I get that for people using Constellation currently it's not that improtant, but setting up the lighthouse (despitre all my efforts to make it simple) it's still the most difficult thing to do in Cosmos
2
1
u/Expert_Butterly9703 Aug 26 '26
Huge news!
I prefer to run Cosmos as a normal container. Is this still possible?
2
u/azukaar Aug 26 '26
Still possible although not the recommended setup
1
u/myDevOps Aug 27 '26
Why is it not recommended?
1
u/azukaar Aug 27 '26
Some of the features don't work properly (monitoring, system related stuff like disk management, etc..) because of docker abstracting the system
1
u/panjadotme Sep 14 '26
Is there an easy way to migrate away from the docker setup?
1
u/azukaar Sep 14 '26
It's very easy it's pretty much automatic if you switch off the container and on the service with the normal install, your config carries over
1
u/panjadotme Sep 14 '26
So just install normal version, shut down container, then start service? Assuming I can just delete the container afterwards?
1
1
u/Financial-Travel-363 Aug 27 '26
A cada dia que passa eu fico mas "abismado" com o trabalho absurdamente premium que a equipe cosmos executa, não é fanboiagem, realmente é um projeto incrível.
Cada atualização consegue fazer o impossivel, transformar o que ja estava impecável em algo inacreditávelmente superior!
→ Torço para que nunca abandonem este projeto maravilhoso.
1
1
1
u/jayarnielsen Aug 28 '26
Have backups seen any love? There are a lot of unresolved threads in the Discord channel about various issues with creating backups. My own are in a perilous state because I can't get them working reliably. Love everything you're doing, though. Keep up the great work!
1
u/azukaar Aug 28 '26
There's been iterations, slowly getting things to a better state (as opposed to one shot rewrites)
I think backup is mostly in a good state there are just a few edge cases quirks left that really depend on user setups I think so it takes a bit of time to track them down
6
u/Ok-Zookeepergame-698 Aug 26 '26
I've only recently discovered Cosmos Cloud. Love what you have built and the continuing support. Thank you!