Classic request for bower

[jdstrand]

@sheerun

b) Allow for access for Bower configuration files:

• Local .bowerrc located in the current working directory
• All .bowerrc files upwards the directory tree
• .bowerrc file located in user’s home folder ( ~ )
• .bowerrc file located in the global folder ( / )

This can be handled via The personal-files interface. Do not that $HOME is set to ~/snap/bower/<revision> and you have full access to anything in this directory, so you may not need personal-files at all for this.

@sheerun

c) Allow access to git configuration (~/.gitignore ~/.gitconfig ~/.ssh) etc. because Bower can use git for fetching dependencies. The same for SVN configuration.

Git can be via the personal-files interface, ssh via ssh-keys or ssh-public-keys.

@sheerun

d) Allow access to environment variables like HTTP_PROXY, but also any other environment variables because they can be used in install scripts configured in .bowerrc

The environment is preserved and with personal-files, you can access .bowerrc.

@sheerun

e) Allow write access to any directories in filesystem as bower_components install location can be freely configured in .bowerrc

Typically using the home and removable-media interfaces is sufficient for things like this.

@sheerun

f) Allow full access to ~/cache/bower

See above about $HOME and/or personal-files

When you’re ready to start looking into this more, I suggest reading Snap confinement | Snapcraft documentation (along with other topics along the left). If you have trouble, please open a new forum topic under the ‘snapcraft’ category so the right people see your questions. You can also search this forum or ask questions in snapcraft on IRC (Freenode). Good luck!