{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/4590c23f60363df38621f12d129f367d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"4590c23f60363df38621f12d129f367d","url":"https://api.github.com/users/averyvery","login":"averyvery","id":72114},"milestone":null,"updated_at":"2011-11-05T15:08:26Z","labels":[],"assignee":null,"comments":2,"closed_at":null,"url":"https://api.github.com/repos/averyvery/freeway/issues/4","body":"As it stands, Freeway loads all config options from the settings page. This is good for EE beginners, but more advanced users will wail and gnash their teeth. Reasons a PHP file would be better:\r\n\r\n- Files can be version-controlled.\r\n- Files are easier to edit. You can edit it them a text editor, add comments.\r\n- Code is more powerful than text. By iterating, you can make a ton of routes with very little code; even generate them based on external criteria (like environment vars, info from the DB, etc)\r\n\r\nFour ways to accomplish this, but I'm leaning towards the first:\r\n\r\n- Ask users to add freeway_routes.php to their /system/expressionengine/config dir. \r\n  - Pros: This is where configs go.\r\n  - Cons: Routes get wiped out if you don't update EE carefully.\r\n- Put freeway_routes into the actual extension dir. \r\n  -  Pros: Easy to find, easy to remember. \r\n  -  Cons: Get wiped out if you don't update Freeway carefully.\r\n- Ask users to supply a path to their freeway_routes file\r\n  - Pros: Users can fit routes into their preferred setup.\r\n  - Cons: Configuring a file path seems completely ridiculous. Seriously, doesn't EE have enough config vars that go wrong?\r\n- Put routes into the config.php itself, as a new config var.\r\n  - Pros: No new files.\r\n  - Cons: Adding non-standard config vars seems like a recipe for trouble. Config.php gets automatically rewritten sometimes.","html_url":"https://github.com/averyvery/freeway/issues/4","number":4,"title":"Optionally load routes from a file","id":2150688,"created_at":"2011-11-05T04:36:45Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/fb7639409626326cf33e2141d8d8728f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"fb7639409626326cf33e2141d8d8728f","url":"https://api.github.com/users/jeremygimbel","login":"jeremygimbel","id":159320},"updated_at":"2011-11-05T15:08:26Z","url":"https://api.github.com/repos/averyvery/freeway/issues/comments/2640799","body":"I would agree with the first option. And as a second choice, the last one.","id":2640799,"created_at":"2011-11-05T15:08:26Z"}}