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

Build project with a fixed path #21

Closed
SimonWpt opened this issue May 17, 2012 · 13 comments
Closed

Build project with a fixed path #21

SimonWpt opened this issue May 17, 2012 · 13 comments

Comments

@SimonWpt
Copy link

It would be great, if I could set a fixed path for project building. I am developing a chrome extension and deploying via Apatana is a little painfull with changing paths:-(

Greetings

Bertram

@William-Owen
Copy link

I agree.

It would be fantastic if the current behaviour of creating time-stamped folders could be supplemented with the option to specify a single target build directory, this would then be deleted and re-created on build.

The option to define a path for the time-stamped folders or the target directory would be great.

These options should be set on a per-project basis, possibly as part of config.rb ?

@hlb
Copy link
Contributor

hlb commented May 29, 2012

Does "delete and recreate" work for everyone?

@William-Owen
Copy link

I can't speak for everyone but as an option that would be very useful.

@SimonWpt
Copy link
Author

"delete and recreate" for a fixed path? Yes:-)

@William-Owen
Copy link

Out of interest is there a work around / hack anyone could suggest as a short term remedy? This is killing my workflow.

I have had a dig around for some sort of config change I could make and looked at apps that might watch the folder and check for a new build_xxxxxxxxxxxx directory and then move it but I can't find anything that would do the job.

Any suggestions appreciated.

@hlb
Copy link
Contributor

hlb commented May 30, 2012

It might be dangerous if user can specify the build location anywhere. Ex: "/", "~/", "c:", ...

We would like to implement in this way:

  • You can create a "fireapp.config" in your project folder
  • There will be a "random_build_folder" option, default: true
  • If you set random_build_folder = false, Fire.app will always generate the build in "build/" folder, not "build_xxxxxx".

Does it work for you?

@SimonWpt
Copy link
Author

Not the easy way, but it is OK for me:)

@William-Owen
Copy link

I am sure that given the options to allow a build anywhere some people could find somewhere silly to build it, but I think that it should be a allowed as this would allow for the best application flexibility.

Other than that I think it would be cool if the file had the following settings

build_folder_path ""

  • If no set this would default to the /build directory based on the application path

build_to_timestamped_folder = true

  • default behaviour, if set to false the code would be built to the root of the build path folder.

@SimonWpt
Copy link
Author

Why not integrating it in the config.rb? There is no need for a new config-file.

@William-Owen
Copy link

I wondered that but I would guess that its not Ruby that would be doing the work.

@hlb
Copy link
Contributor

hlb commented May 31, 2012

@SimonWpt because config.rb is compass's config file, and we don't want to mix it.

@lggarrison
Copy link

I would like the option to define a path for the time-stamped folders. Thanks.

@hlb
Copy link
Contributor

hlb commented Jun 22, 2012

It is done in Fire.app 1.2, but there is no UI option (yet).

HOWTO: You can add fireapp_build_path="foo" in config.rb, and it will build project to project_path/foo. When Fire.app build a project, it will delete the folder first, then regenerate it.

DANGER: If you add fireapp_build_path="/path/to/build/folder/path" in config.rb, it will build project to /path/to/build/folder/path. If you write "/Users/foo", your home folder may be removed.

@hlb hlb closed this as completed Jun 22, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants