| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
[load] require login_format_validation in session
We moved it into the lib folder so it's not in an autoload path anymore.
So now it needs to be required before being used.
This fixes a load order issue that would cause non-deterministic failures
in CI
See merge request !6
|
|
We moved it into the lib folder so it's not in an autoload path anymore.
So now it needs to be required before being used.
This fixes a load order issue that would cause non-deterministic failures
in CI
|
|
Bugfix/send 406 on unsupported format
See merge request !5
|
|
If you inherit respond to and call it again in your controller
it will not overwrite the previous but add to it.
Since we always have some exceptions from the rules it's probably
easiest to be explicit in the controllers that require it themselves.
|
|
It used to run the action and then trigger a 500 because the
template was not found.
fixes !3 .
|
|
Upgrade/rails 4
See merge request !4
|
|
|
|
|
|
Cleanup/ci files
See merge request !3
|
|
|
|
This is supposed to fix the bundler error reported in
https://github.com/bundler/bundler/issues/3558
sudo: false makes travis use the new infrastructure without sudo
|
|
|
|
|
|
[ci] get gitlab to run tests
See merge request !2
|
|
This makes writing the tests for database names easier as they should
be the same strings on gitlab, travis and locally.
|
|
use_database affects all uses of prepare_database - so also the one
in tmp_database. In order to avoid that we do not use_database but
just overwrite the database method itself.
|
|
|
|
It was causing 404s on initializing the database with db:migrate.
DatabaseMethods rewrite of #database does not call prepare_database
and thus does not create the database when needed.
DatabaseMethod is also quite a bit too much for a model that has
two databases that can be memoized easily. There's no way to have
a separate database instance per record.
|
|
We already did the same for other concerns. The way we load models
for couchrest migrations does not work well with concerns in the
model directory as they will be loaded twice.
|
|
Couch docker image will be available on the host called couchdb.
So we use curl to check for it and display the version string.
And then we move a couchdb.yml config file into place so the right host
will be used.
|
|
|
|
for him/herself
So that it we do not expose the is_admin property to anyone else
including other admins.
|
|
feature/expose_admin_in_api
|
|
|
|
|
|
|
|
|
|
|
|
Thanks a lot!
First small text fix from the Rails Girls Summer of
Code team Load to Code from Berlin
|
|
|
|
Fix install issue and update the documentation
During the rails 4 update db:migrate stopped working because the way couchrest loads all models broke. This includes a fix and also updates the install instructions.
I tried to separate advanced topics in development from the others by marking the sections (advanced) in doc/DEVELOP.md
|
|
|
|
|
|
|
|
We saw errors from duplicate loading of LocalEmail and
LoginFormatValidation. The latter resulted in a crash.
In an attempt to ensure all subclasses of Couchrest::Model::Base are
loaded Couchrest::Model::Utils::Migrate requires all files in app/models.
We have an extension that does the same for the engines.
During this process LoginFormatValidation and LocalEmail were autoloaded
when 'identity' was required. Afterwards they were required again.
It looks like rails' autoload mechanism does not play nicely with require.
So to make sure they are not autoloaded first move the concerns and
helper classes into the lib directory and require them explicitly.
|
|
|
|
|
|
They led to some install issues. No need to pick a server for dev env.
|
|
So that whoever consumes the API can use this attribute to
determine if admin functionalities should be made available to
the current user.
|
|
with_config is not mean to test the current config. It will
set the config. So instead we need to look into APP_CONFIG.
|
|
This expresses the intent rather than the implementation.
Also replace temp with query refactoring.
|
|
There was a lot of special case handling going on in the users_controller
for this. Lot simpler this way.
|
|
There's no route to this right now and it also seems to be tested
nowhere. Since i am about to split up the users_controller let's
get rid of this and put it in the place we want it once we actually finish
the implementation
|
|
Actually this should live in a service_level_controller.
For now fix the security issue.
|
|
|
|
MX validations relied on network connection. Only using them
in production environment now. I want to be able to develop and
test when disconnected.
|
