You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
I think we need to have a discussion on the topic of shipping a pre-baked config file.
It's no good to assume that the installation path is a sane choice for uploading files to, when there might be other config items in the future for which we don't have sane defaults. This is why I think we should discuss future features and resulting config entries and vet the idea thoroughly.
On the topic whether the installation path is a sane default:
In most *nix systems, code/software and data are at least somewhat separated. Which makes sense, because the software partitions are not written too as frequently as the data partitions. Also, the amount of disk space needed for the two differ greatly.
In my opinion, this separation is valuable and makes sense for most setups.
By defining a default value, we're not forcing the user to use the installation directory, but it might be misleading to some. Maybe we should present the user with a setup assistant when the Pynitus App is first accessed after installation to encourage users to decide for themselves?
I'm not decided on the issue yet and I'd like to hear further discussion on it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would make it possible to move around a complete, valid pynitus-instance by moving the root folder, which would have some benefits..
How do you think about it?
The text was updated successfully, but these errors were encountered: