Is this feature request related to a new or existing Amplify category?
New category
Is this related to another service?
No response
Describe the feature you'd like to request
Move the .amplify directory from the user's home directory to another location, by default, or via a environment variable / CLI argument.
Describe the solution you'd like
The CLI creates a directory in the user's home directory called .amplify.
A more appropriate location would be .local/share/amplify, according to the XDG spec.
The bin, lib and logs subdirectories of .amplify could also be split among the standard contents of the .local dir.
An easier and quicker solution, that most would find sufficient is to allow for the location of the .amplify folder to be configured via a config file, environment variable, or command line argument. In that case; the structure would not be altered and the default could remain the same; in case that's important for backwards compatibility or something else.
Describe alternatives you've considered
I could find no information that suggests that this is currently possible. One alternative is to use symlinks, but that is not a solution for those intent on reducing clutter in their home directory.
Additional context
No response
Is this something that you'd be interested in working on?
[ ] 👋 I may be able to implement this feature request
Is this feature request related to a new or existing Amplify category?
New category
Is this related to another service?
No response
Describe the feature you'd like to request
Move the
.amplify
directory from the user's home directory to another location, by default, or via a environment variable / CLI argument.Describe the solution you'd like
The CLI creates a directory in the user's home directory called
.amplify
.A more appropriate location would be
.local/share/amplify
, according to the XDG spec.The
bin
,lib
andlogs
subdirectories of.amplify
could also be split among the standard contents of the.local
dir.An easier and quicker solution, that most would find sufficient is to allow for the location of the
.amplify
folder to be configured via a config file, environment variable, or command line argument. In that case; the structure would not be altered and the default could remain the same; in case that's important for backwards compatibility or something else.Describe alternatives you've considered
I could find no information that suggests that this is currently possible. One alternative is to use symlinks, but that is not a solution for those intent on reducing clutter in their home directory.
Additional context
No response
Is this something that you'd be interested in working on?
Would this feature include a breaking change?