You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason it hasn't happened is that Arc tends to encourage us to stay close to the codebase so that we gradually come to understand its internals. Configuration variables in code are just one aspect of that ethos. Do you have some context that prefers isolating configuration variables from code?
Sometimes the best way to figure out why things are the way they are is to change them and see if somebody complains. In code, changing and reverting are easy operations.
@bzg, I think that is a great idea. If you are running a News site, you basically lose your site configuration every time you do a git pull. It's just not a good idea to have the config in the same file as the code.
Good to know this is a source of pain. I haven't spent any time maintaining a News app. I believe the recommended solution is to run off a branch that you periodically merge master into.
news.arc
contains configuration variables likethis-site*
.I think it would make sense to store configuration variables in a separate file.
What do you think?
The text was updated successfully, but these errors were encountered: