Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Ability to have truffle migrate use a user defined configuration file. #1879

Closed
1 task
caleteeter opened this issue Apr 4, 2019 · 3 comments
Closed
1 task
Assignees
Labels

Comments

@caleteeter
Copy link


Issue

Truffle currently relies on truffle.js or truffle-config.js for the configuration elements that are used for compliation and migrations. Having a global configuration flag that would allow truffle to use user passed in configuration file path.

Steps to Reproduce

Expected Behavior

Addition of a global configuration flag such as this: truffle migrate --config</path/to/config>

Actual Results

Loading truffle configuration settings from user defined configuration files.

Environment

  • Operating System: Windows
  • Ethereum client: N/A
  • Truffle version (truffle version): 5.0.8
  • node version (node --version): 10.13.0
  • npm version (npm --version): 6.9.0
@eggplantzzz
Copy link
Contributor

eggplantzzz commented Apr 24, 2019

@caleteeter Thanks for the suggestion, it seems like a good idea! We'll look into it.

@CruzMolina
Copy link
Contributor

Requirements

  1. Enable successful usage of a global configuration flag while calling truffle migrate.

Example:

truffle migrate --config /path/to/config
  1. Throw a helpful Error if a truffle config is not found at the given path.
  2. Add an integration test to verify proper behavior (i.e. when passed a valid config path, migration succeeds, when passed an invalid config path migration fails).

Prerequisite Context

@eggplantzzz
Copy link
Contributor

A feature resolving this was released a number of versions ago. Use the --config flag on the command line to specify a path to the Truffle config to be used.

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

No branches or pull requests

3 participants