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
{{ message }}
This repository has been archived by the owner on Apr 16, 2019. It is now read-only.
When working with multiple deployment locations, having a single config file is rather frustrating. It would be nice to have _production.py, _staging.py, _development.py config files to solve this problem.
I am trying to integrate blogofile in to a production environment where I automatically stage all changes made to the repository, with periodic releases to a production web server.
Adding a --config-file parameter to the blogofile command would also allow the site to be built using different configurations.
This may be too complex for a project like Blogofile, which aims for simplicity, but the change would not impact users who do not need the feature.
The text was updated successfully, but these errors were encountered:
When working with multiple deployment locations, having a single config file is rather frustrating. It would be nice to have _production.py, _staging.py, _development.py config files to solve this problem.
I am trying to integrate blogofile in to a production environment where I automatically stage all changes made to the repository, with periodic releases to a production web server.
Adding a --config-file parameter to the blogofile command would also allow the site to be built using different configurations.
This may be too complex for a project like Blogofile, which aims for simplicity, but the change would not impact users who do not need the feature.
The text was updated successfully, but these errors were encountered: