-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Added support pg from box and update installation doc #1623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… migration. No need increase column size.
|
Looks like a hack. What about |
- Add project name to event title - Push: Entry links to single commit or commits overview depending on number of pushed commits - Push: Display first 15 commits with commit message and author and link to single commit - Issues: Display issue description
This reverts commit 187e192. [ci skip]
Apparently it didn't get removed after the rename to ExtractsPath.
… matches the progress bar
* support/postgres_db: (34 commits) add sqlite to tests test postgres Fix dashboard atom feed routes Do not allow removal of a project owner user. API: add project snippets listing projects API should return info about deleted hook add API changelog Doc fix: Nginx init script requires sudo Tiny fix to the add/edit groups form path field reversed order of progress indication for visual harmony so that text matches the progress bar move emoji module to lib no need to add fonts to assets path improve emoji checking performance specify HTTP verbs for match in routes Fix tests Remove leftover ref_extractor_spec file Revert "Use official Grit 2.5.0" ExtractsPath: Use ref_names instead of branches+tags Fix bug with branches whose name contains slash added trace to travis ...
thx
added. What about autoupdate db/schema with run rake db:migrate?
yes. With fix models. Code attached. p.s. updated to upstream. |
when you run db:setup then schema.rb will be used. |
|
Ok. Code updated. But after run rake task this hack will be overwritten… May be not use rake db:setup?
We can create db, run migration and load seed data… This would be equivalent, but it will not be necessary to remember about the hack ... С наилучшими пожеланиями, Андрей Куманяев. On Tuesday, 9 October 2012 г. at 0:47, Valeriy Sizov wrote:
|
|
migrations is not an options. DB should be build from schema for new instances. |
It is quite possible, especially if used in the migration models that have been removed or rewritten so much that the fall migration to fail. But you do not have the practice of zero migration? not always possible to use the scheme because schema.rb not affect things that are not described in the DSL. such as triggers. this way means that it is often necessary to move away from the side rb to sql schema (migration). it is changing the config.
If we have to work correctly migration or zero migration - the launch rake db:create && rake db:migrate && rake db:seed will not only bring the same result, but it could be better. |
|
Added support postresql database from box installation without error and updated installation doc