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
@nicolas2lee I see you started adding a Vagrantfile to run the server in the develop branch. That seems like a sensible thing to have. Did you get it working? Is it ready to merge? We're working on the master branch for the main development.
Is putting the production secret key in the repository a cause for concern? The comment just above that seems to say that's not a good idea.
The text was updated successfully, but these errors were encountered:
Vagrant is just a tool for development, vagrantfile is useful only when someone like me use vagrant to develop. Anyway I do not think vagrant is used for production.
The vagrant config works in my part, if you need vagrant, then maybe you could merge it. Otherwise I think it my stay in the develop branch, since I do not have enough time to work on the project.
The production secret key should never been put in the repo, anyway it should be configured in the production server.
I do not know how you organize branches. But for me, at least, a branch iso-prod (e.g.: master) where the code is same as production code except some secret configs, a branch develop which is the main development branch. Developers should not commit on develop branch (when a lot of things added) directly, a new branch for a new feature, once validated, merge into develop branch, once delivered on prod, then merge into master.
I think I use master the way you use develop, and tag a release when you would merge into master.
We've found some local Ruby developers who're interested in helping us develop the site for this year's competition. So I'll leave this open for now and they can decide whether they want to use a Vagrantfile.
@nicolas2lee I see you started adding a Vagrantfile to run the server in the develop branch. That seems like a sensible thing to have. Did you get it working? Is it ready to merge? We're working on the
master
branch for the main development.Is putting the production secret key in the repository a cause for concern? The comment just above that seems to say that's not a good idea.
The text was updated successfully, but these errors were encountered: