[Script request] Cosmos

[Olaipai]

Application Name

Cosmos

Website

https://github.com/azukaar/cosmos-Server/

Description

Disclaimer: I am not associated nor affiliated with this project. I just think it is seriously cool!

Cosmos Cloud is a really neat and cool project that furthers expand the self-hosted cloud docker idea and solves the problem of insecure and vulnerable self-hosted services and servers.

Instead of just helping with the initial docker compose it also comes with a lot of neat features such as strong security with auth servers (MFA, SSO, 2FA), reverse proxy, gateway, docker- & storage- management, rclone, cron, openIP, App Marketplace, monitoring of services and a bunch more like bot and (D)DoS protection, HTTPS w/ Let's Encrypt.
It also has a really cool API security feature that they call SmartShield!
Cosmos Cloud (server) is a more complete / turnkey-esque option to CasaOS, Unraid and Yuno.
It also features a VPN called Constellation based on Nebula, however this seems to be a paid feature (Lifetime or subscription). The more advanced storage features such as remote storage also seems to be a paid feature.

I came over this project as I wanted to explore the cloud and web services out there but was put of when I realized it would turn into even more maintenance and stress. I just wanted something with low maintenance and with most of the security handled out of the box. And Cosmos hit the nail on the head!

I believe this project will be really helpful to Proxmox users as it runs flawlessly in a LXC unlike CasaOS. So with this project will take out associated stress, danger and time for a beginner (or advanced users) to setup their own cloud and web services. It made the setup of HTTPS and SSL a breeze with Let's encrypt. They also seem to have great documentation.
It is fully secure and has automated maintenance right out of the box!

It is easy and simple to use but also packs a ton of features for the more adventurous and experienced user if they so choose to!
It reminds of Home Assistant except for self-hosting.

Cosmos official website
Cosmos UI Demo

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.
• This is not a game-related request.

[di5cord20]

I've used cosmos for some time and can attest to both the simplicity and features it provides. What makes it more interesting now is that the developed introduced a bare metal option in version 17. The bare metal is in beta currently and he plans on taking it out of beta next week.

I have the beta running in an LXC and it works well. Happy to help answer questions or support if needed.

[azukaar]

Hi! Dev here, thanks for the suggestion @Olaipai, I'm available to support if needed

[di5cord20]

Forgot to mention, Cosmos also provides .local domain support out of the box. The script should likely include setup for Avahi to support per https://cosmos-cloud.io/doc/2%20setup/#optional-local-domains

[michelroegl-brunner]

@azukaar I grep your github releases for the latest version. We do not have CPU passthrough set up yet. This is only a DEV instance atm, not final.
We are discussing atm if we will add or not. We have the policy to only offer "Bare Metal" installs without docker out of the Box. Do you plan on publishing a guide wich covers dependencys and all that for the dockerless version.
Also, can i supply a config file with database credentials and all other things so we can have that dockerless also?

@di5cord20 i dont know yet if privileged is needed. Finally, what should the default RAM, CPU, and Storage amounts be set for? That we have to try what fits best. Regarding the Avahi, i would leave that out atm.

[azukaar]

I'm working on the doc for the standalone service install as we speak, here's the relevant excerpt below
And yes you can create a config that pre-install a DB without docker to include that fully docker-less
What does privileged do exactly?

EDIT: full doc here https://cosmos-cloud.io/doc/1%20index/

[di5cord20]

@michelroegl-brunner , I'm curious how this script is progressing. I'd like to help if possible, even if just to test.

[di5cord20]

DEV Version can be tested here bash -c "$(wget -qLO - https://raw.githubusercontent.com/michelroegl-brunner/ProxmoxVE/refs/heads/DEV/ct/cosmos.sh)"

I tried but couldn't access the script. Again, happy to help if and where I can if possible. @azukaar released v0.18 beta today and is looking for testers. I was hoping to use this script (and modify to pull the beta 0.18 release) for that purpose.

Edit: adding link to latest beta release azukaar/Cosmos-Server@70a0848

[michelroegl-brunner]

For now, we have decided not to include Cosmos as a direct installation script due to its strong dependency on Docker. Our philosophy is to install all applications natively.
If you wish to use Cosmos with our scripts, you can create an LXC container using our Debian or Ubuntu scripts and then run the following command inside the LXC shell to install Cosmos: curl -fsSL https://cosmos-cloud.io/get.sh | sudo -E bash -s

[di5cord20]

Thanks @michelroegl-brunner . I respect the community decision. I am a bit confused though as Cosmos doesn't have any dependency on docker (per se). The way I see it, Cosmos has the ability to manage docker apps similar to Dockge or Komodo except, unlike those apps, Cosmos is installed natively (I believe Dockge and Komodo are docker apps themselves and not installed natively... I could be wrong).

Again, I don't have the skills to create the scripts so am just sharing my thoughts. As you rightfully pointed out, installing Cosmos is very straight forward as the developer made it very easy for users.

Thanks again.

[azukaar]

The only thing it does is install a MongoDB container (not postgres) during the install UI process, at the request of the user. That DB can be substituted for any other Mongo instance, including non-docker, at any moment (even before the install wizard is run, the DB will be detected and the DB step of the install wizard skept)

[michelroegl-brunner]

Yep, sorry for that, i did not remember correctly. Is there a way to skip the initial dialouge and do the settings for the db directly?
I´m not using your install script directly, i have rebuild it to fit our needs.
To skip the webui install if we can.

[di5cord20]

The web ui step 3 sets up the ssl cert Cosmos uses. The ease of getting the Letsencrypt cert functioning was what initially drew me into Cosmos (was easier than Traefik or Caddy).

I'm curious what the user experience would be like if that step was automated as part of the lxc or vm script setup.

• Would it prompt for the details itself? That might be too complicated due to all the possible options.
• Alternatively, the script could opt for the 4th option to setup HTTP only and then instruct the user to change manually after install if they'd like to do so.

Personally, I'd be okay to run the web ui setup myself per native Cosmos approach. I mean, if I'm installing the app, I likely know why I'm doing so and would be expecting to configure it per the app's instructions.

What do you think?

[azukaar]

@michelroegl-brunner Yo udont need to skip the install UI, it is not part of the script, it is part of Cosmos itself on the first boot. And it will auto-skip the DB part if the DB has been added to the config prior to starting it

@di5cord20 no it would not automate that part, only the DB part

[michelroegl-brunner]

Yes, its fine by me. Where can i find the config file then? I was not able to find it.

I got it installed tough: https://github.com/michelroegl-brunner/ProxmoxVE/blob/develop/install/cosmos-install.sh

[azukaar]

It's in /var/lib/cosmos, you can change the "MongoDB" line in the JSON to be the full connection URI

[michelroegl-brunner]

I am assuming it is because you don't uncheck "fresh install" which wipes the settings?

Otherwise this looks valid

By unchecking "fresh install"' wouldn't the user have to manually do steps 3 (HTTPS) and step 4 (setup admin account)? I know it's possible, but something the community script and users would need to be mindful of. Once the script completes, the default admin id and password would need to be provided with a recommendation to update.

Assuming the above is correct and to keep things simple, should the community script exclude the mongo db install and just allow the cosmos fresh install to do so using the approach all Cosmos users currently follow?

We normaly install all scripts with http and auto generate user and passwort or use generic one. We have such a system in place with many scripts.

To your second part. We try to keep all things bare metal, we try to avoid scripts wich reliy enterly on provided install scripts. In this case you also could install a Debian lxc and run the app install script yourself, wich is basicly just a oneliner.

[azukaar]

@di5cord20 No they wouldn't have to the UI wizard will still work

[michelroegl-brunner]

So i got it to accept my mongo db string and set NewInstall to false. The service starts and the Webpage is reachable in browser.
But it dose not start the UI wizard, instead it now pormpts for a user.

And i have no idea where to set this user. I did not see anything in the config and the mongo DB seams to be empty.

Can you point me in the right direction?

[azukaar]

You cannot set NewInstall to false because then you are skipping the entire wizard. You have to let the user get throught it so they can create their user (and also select their HTTPS settings)
What were you trying to do exactly? If you were trying to prevent the DB line from being erased, the "Fresh Install" I was talking about is this:

[michelroegl-brunner]

Ah, thats on me then. I completly misunderstood you, I thought you were talking about the config file.

[michelroegl-brunner]

Is merged :)

[michelroegl-brunner]

I just took the service file wich cosmos made when running there install script. But i can check next week

[azukaar]

The service is called CosmosCloud not CosmosService

[michelroegl-brunner]

Ah okey. i change that.

[azukaar]

I think you have nothign to change @michelroegl-brunner , just @di5cord20 was using the wrong command

[di5cord20]

My mistake... but same result.