Skip to content
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

Why are absolute paths not supported? #112

Open
localhosted opened this issue Dec 7, 2017 · 3 comments
Open

Why are absolute paths not supported? #112

localhosted opened this issue Dec 7, 2017 · 3 comments

Comments

@localhosted
Copy link

Why are absolute paths not supported? I've read the comment, but why can't you just pull in the files from a directory? I have frontend code that's in a different project/vcs and I'd like to just pull the built files when running my backend code.

go.rice/box.go

Line 33 in 9fdfd46

if filepath.IsAbs(name) {

@GeertJohan
Copy link
Owner

I'm nut sure if there was anything holding this back, or just a philosophical decision. A proof-of-concept / PR is welcome :)

@GeertJohan
Copy link
Owner

Although I'm wondering if this follows the right philosophy for development. The idea is that in a live development environment, rice can find the assets by import path.
So perhaps we should first create a proper design/rationale on as why to do this? Are the assets not part of the development cycle? Will they be on the same absolute path for every developer on the project?

@InterwebCounty
Copy link

I wanted to use it in a desktop app and needed an absolute path to os.UserHomeDir() + "/Library/Application Support/".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants