Remove database from master in favor of direct hosting sync with Production
@MananSoni42 take note of the new structure of branches. From now on:
Any change to database, the change in database_update has to be on master, and its corresponding .json change will go into production
Any updates to menu will go directly to production
Any changes to dictionaries (.txt) will go directly to production
Any change in media files (BOBFiles) has to be pushed to master, since we can host media files on GitHub pages only via master. This is a flaw. Propose a better solution if you come across any
The restriction of no push access to master is still there. Let me know if you want it to be removed
Note: Heroku is now in direct sync with production branch.
Remove database from master in favor of direct hosting sync with Production
@MananSoni42 take note of the new structure of branches. From now on:
database_update
has to be on master, and its corresponding.json
change will go intoproduction
production
.txt
) will go directly toproduction
BOBFiles
) has to be pushed to master, since we can host media files on GitHub pages only via master. This is a flaw. Propose a better solution if you come across anyNote: Heroku is now in direct sync with production branch.