Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Installer #2

Open
lleyton opened this issue Sep 23, 2022 · 9 comments
Open

Custom Installer #2

lleyton opened this issue Sep 23, 2022 · 9 comments
Assignees

Comments

@lleyton
Copy link
Contributor

lleyton commented Sep 23, 2022

Anaconda, Fedora's installer, isn't great UX wise. There's an opportunity for us to significantly improve the installation experience (and maybe even the speed too) through our own installer.

@korewaChino
Copy link

This would be pretty hard to do. Anaconda does everything from boot configs to package setup.

We can probably just make a new installer frontend based on the Anaconda API, but the API is still not stable.

@lleyton
Copy link
Contributor Author

lleyton commented Sep 24, 2022

Hmmm, fair point. I think it might be worth it to use Anaconda's API with our own frontend, even if it's unstable.

@lleyton lleyton added enhancement New feature or request and removed enhancement New feature or request labels Sep 24, 2022
@korewaChino
Copy link

Recently, Anaconda has added a Web UI functionality, so we can probably look into how they work with Cockpit and replicate the API for ourselves.

@nothingneko
Copy link
Contributor

We have a couple different designs, here's a sampling

Lains' design
installer_1

Jaiden's designs
Installer Cold Open
Installer
Installer Prog

@lleyton
Copy link
Contributor Author

lleyton commented Mar 21, 2023

Honestly, I feel like picking this up, need a new tau project to work on :p

I'm still undecided if I want to use anaconda or not as a backend

@nothingneko
Copy link
Contributor

Anaconda is incredibly customizable, but you'd have to use python. What I'm thinking we can do is a dual backend system. On tauOS we manually deploy the OSTree to the drive. On Ultramarine we can use distinst

@lleyton
Copy link
Contributor Author

lleyton commented Apr 7, 2023

I see no reason why we couldn't use distinst for this as well, since it takes a squashfs for deployment in which we could stage an OSTree deployment on.

@lleyton lleyton self-assigned this Apr 7, 2023
@nothingneko
Copy link
Contributor

Sounds good to me

@korewaChino
Copy link

UPDATE: Please see https://github.com/FyraLabs/readymade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants