11 Apr, 2016
1 commit
08 Apr, 2016
1 commit
07 Apr, 2016
1 commit
24 Mar, 2016
1 commit
16 Mar, 2016
1 commit
15 Mar, 2016
1 commit
08 Mar, 2016
1 commit
29 Feb, 2016
1 commit
23 Feb, 2016
1 commit
22 Feb, 2016
1 commit
28 Jan, 2016
2 commits
-
This will avoid, or at least reduce the chances of, having the CI builds falling over on temporary network failures.
26 Jan, 2016
1 commit
22 Jan, 2016
2 commits
-
Conflicts: Gemfile.lock db/schema.rb plugins/community_hub
19 Jan, 2016
1 commit
08 Jan, 2016
1 commit
05 Jan, 2016
1 commit
-
Depending on the setup PostgreSQL might still be starting up when we get to the first point where Rails will try connecting, and will fail with: PG::ConnectionBad: FATAL: the database system is starting up So we wait for PostgreSQL to be ready.
30 Dec, 2015
2 commits
14 Dec, 2015
4 commits
10 Dec, 2015
2 commits
09 Dec, 2015
1 commit
23 Nov, 2015
1 commit
17 Nov, 2015
1 commit
-
Conflicts: Gemfile Rakefile app/controllers/box_organizer_controller.rb app/controllers/my_profile/tasks_controller.rb app/controllers/public/profile_controller.rb app/mailers/user_mailer.rb app/models/article.rb app/models/person.rb app/models/product_category.rb app/models/task.rb config/application.rb config/routes.rb lib/acts_as_having_settings.rb lib/noosfero/api/entities.rb lib/noosfero/api/helpers.rb lib/noosfero/api/session.rb lib/noosfero/api/v1/articles.rb lib/noosfero/api/v1/contacts.rb lib/noosfero/api/v1/search.rb lib/noosfero/api/v1/users.rb test/functional/tasks_controller_test.rb test/unit/api/articles_test.rb test/unit/api/helpers_test.rb test/unit/api/people_test.rb test/unit/api/search_test.rb test/unit/api/session_test.rb test/unit/api/users_test.rb test/unit/person_notifier_test.rb test/unit/task_test.rb vendor/plugins/access_control/lib/acts_as_accessible.rb
12 Nov, 2015
1 commit
-
People that are using an old enough noosfero tree might have problems with it.
11 Nov, 2015
1 commit
-
We can now just search for "****"
10 Nov, 2015
3 commits
-
I wasn't able yet to figure out why the rake task was not behaving as expected. I suspect it has to do with the order stuff is being loaded being changed with Rails 4, but I am not sure yet. This works.
-
Fixes whenever in production for a multitenancy setup Each cronjob has to run for all production environments. Currently they are only running for the environment named production so it doesn't work in a multitenancy setup. I use `whenever --update-crontab` to append jobs for each environment, using the environment name as a whenever identifier, and then I have to clean the crontab of each environment generated jobs using the same identifier. See merge request !705
-
Each cronjob has to run for all environments. I use `whenever --update-crontab` to append jobs for each environment, using the environment name as a whenever identifier, and then I have to clean the crontab of each environment generated jobs using the same identifier.
09 Nov, 2015
1 commit
04 Nov, 2015
1 commit
03 Nov, 2015
2 commits
29 Oct, 2015
1 commit
15 Oct, 2015
1 commit