-
Notifications
You must be signed in to change notification settings - Fork 177
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
fix: moving recipe back to a directory available on the host #36
Comments
I like the concept of /.well-known/ so maybe we should copy it to /well-known/ (without the dot). There it would be accesibke for everyone. |
Isn't well-known related to webserves and SSL? I'd prefer a standard Linux root directory. I'm thinking just
|
Or /var/ because it's a file that can change. |
Var is not something we can write to, and the file shouldn't be changed by the user on the computer (does nothing), only in git.
Not just putting it to |
Currently the
just setup-flatpaks
command is broken (because of e9c31ab). In light of this, the recipe should probably be moved to some folder accessible on the host computer.That folder probably shouldn't be
/etc/
, though, as that implies that it's a config file that can be edited, when it should only be changed inside the git repository.The text was updated successfully, but these errors were encountered: