✨ Added nix package

[xaiyadev]

Fixes - #4

---

• __Luna.registerNative': Error: EROFS: read-only file system
• Add GitHub workflow for flake update
• (not big deal) Create modules for nix
• Add documentation for installation in nix

__Luna.registerNative': Error: EROFS: read-only file system

When creating a package with NixOS it is stored in /nix/store, that folder is completely read-only
This software now tries to change some files that are now in the store...

Is there a way to move the files that needs to be edited in a /tmp folder or in the home directory itself?
Or is there any other suggestion to fix this error?

[github-actions]

Your PR's base branch was set to master, PRs should be set to target the dev branch.
The base branch of this PR has been automatically changed to dev, please check that there are no merge conflicts

[Inrixia]

Is there a way to move the files that needs to be edited in a /tmp folder or in the home directory itself? Or is there any other suggestion to fix this error?

Yes, but only if you are OK with not being able to update within the client as the client needs write perms on the folder to do so.

[xaiyadev]

Is there a way to move the files that needs to be edited in a /tmp folder or in the home directory itself? Or is there any other suggestion to fix this error?

Yes, but only if you are OK with not being able to update within the client as the client needs write perms on the folder to do so.

I would love that!
A solution maybe would be to add some sort of reload button into the config page?

Or maybe add some sort of try/catch that checks if you have read permissions and work with that then (first check if the home config folder where we would store the data has write access, if not resort to the opt/folder?

That way we could add a module system into nix too!

[Inrixia]

I would love that! A solution maybe would be to add some sort of reload button into the config page?
Filesystem write is only needed for loading native plugin code, which most don't need and is due to me just cheating to fix another issue.

ATM its using the app dir because its there and simple. But changing that to the OS temp dir is better and something I was planning to do anyway. Doing that should remove any issues with needing fs write.

[xaiyadev]

I would love that! A solution maybe would be to add some sort of reload button into the config page?
Filesystem write is only needed for loading native plugin code, which most don't need and is due to me just cheating to fix another issue.

ATM its using the app dir because its there and simple. But changing that to the OS temp dir is better and something I was planning to do anyway. Doing that should remove any issues with needing fs write.

Wouldn't it be smarter than to add it into the home config?
That would always help with different users wanting different configurations

[Inrixia]

The temp dir used only has files appear momentarily they are writtern, read and deleted immediately.

So moving is to OS tmp makes the most sense.

[Inrixia]

Hey, sorry been busy. Did you get the chance to review my last review comment?

[xaiyadev]

Hey, sorry been busy. Did you get the chance to review my last review comment?

Yes, been busy myself lately
Right now I am searching for a solution that does not use the hashes and builds the project in the flake
Struggling with that a bit, maybe will throw that away too

I could, for the mean time, add something sloppy that would work, but is not really beatiful

[Inrixia]

Ah great 😊 and no problem or rush, just checking in.

Def get something you are happy with there's no need to push it out quickly.

Appreciate the help and effort on this too!

[Inrixia]

This is looking awesome

[Inrixia]

Lmk when it's ready to merge and we can test if the workflow properly updates the file

[xaiyadev]

Last things missing:

• NixOS Modules
• Documentation entry

NixOS module needs the fix for the Entry thingy we talked about
And I would write the documentation after I am done with the nixos Module

[Inrixia]

FYI (idm since I can just squash it or whatever) but for future prs it can be a good idea to make a new seperate branch on your repo so you don't run into pulling commits from a remote branch into the pr :)

[xaiyadev]

Yeah, already noticed that when it was to late
Will do that for my next PRs

[xaiyadev]

Will add the modules part later in another pull request
So this can be merged!

[xaiyadev]

(Also added devenv files, making that I have the right packages for developing, if you dont want them in your repo I can remove them)

[Inrixia]

This diff is really messy due to mixed dev commits. Could you try merge dev into your branch, to isolate out just your changes. Or make a new branch and change this pr to use that ❤️

[Inrixia]

Please bring this file back

[Inrixia]

I'll trust this is clear enough for the average nix user.