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

API: Allow and/or prefer to use a standalone file for configuration #6

Open
lessp opened this issue Jun 3, 2020 · 0 comments
Open

Comments

@lessp
Copy link
Member

lessp commented Jun 3, 2020

As to separate the logic and not clutter up esy-configurations I propose that we either allow for a separate config-file to be used, or refactor to only use a configuration-file.

E.g.

revery-packager.config.json

{
   "bundleName":"ExampleApp",
   "bundleId":"com.example.app",
   "displayName":"Revery Example App",
   "mainExecutable":"App",
   "windows":{
      "packages":[
         "zip"
      ],
      "iconFile":"assets/icon.ico"
   },
   "darwin":{
      "packages":[
         "tar",
         "dmg"
      ],
      "iconFile":"assets/icon.icns"
   },
   "linux":{
      "packages":[
         "tar",
         "appimage"
      ]
   }
}
@lessp lessp changed the title API: Allow and or prefer to use a standalone file for configuration API: Allow and/or prefer to use a standalone file for configuration Jun 3, 2020
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

1 participant