| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The UUIDResolver adds a route at `/by-uuid/:uuid` that enables
applications to request information about a given UUID.
The UUID must be a Random UUID (version 4, see RFC 4122).
If an invalid UUID is given, the controller will return 422 Unprocessable Entity.
If a valid UUID is given:
- 404 indicates that the UUID is not assigned to anything known to the system.
- 302 indicates that the UUID was assigned to a record, and the User-Agent
will be redirected to that record's Location as indicated in the response header.
- 200 indicates that the UUID was assigned to more than one record (which is unlikely)
and will list those records.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
Just keep it around but do not use it.
It requires `yarn add webpack-bundle-analyzer -D` to install.
Moving `* /` to `*/` will disable the JavaScript comment.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using both the asset pipeline and webpack is confusing
and leads to unpredictable results in production.
This commit moves all (S)CSS to Webpack under `app/javascript/scss`
so that we can test whether the development interface results
in a consistent production deployment.
In order to load the ForkAwesome fonts we used a long path:
`$fa-font-path: "../../../node_modules/fork-awesome/fonts";`
Not sure whether this works...
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This commit add StimulusJS interaction for the map
and taxonomy, as well as styling.
It provides preliminary work to hook up live data on the map
from the taxonomy.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Switching current Agent can help with roles and resource access.
Go to your dashboard by clicking the avatar.
Select agent and hit "Select"
|
|
|
|
|
|
|
| |
Since an Agent is required for all records, we scope the routes
and get it present for free ;)
This commit also adds resource views.
|
|
|
|
|
| |
A single worker in development enables in-context debug in the
error console in the browser.
|
|
|
|
|
|
|
|
|
| |
Since we're dealing with lots of resources, we need a way to
handle pagination. This gem seems to be the new kid on the block
and doing things right, including pagination by default an I18n
support. Let's see.
Kaminari: https://github.com/kaminari/kaminari
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is a first version of the application, to go beyond simple authentication.
|
|
|
|
|
|
| |
Rails.application.credentials.talk_api_key is the key for user interaction
Rails.application.credentials.talk_api_admin is the username to use for administration
Rails.application.credentials.talk_api_admin_key is the admin API key
|
|
|
|
|
|
|
|
|
|
|
| |
The ApplicationController provides a `current_user` method (and
helper) to access the authenticated user (if any).
The WelcomeController provides minimal logic to authenticate
against DiscourseSSO.
Current state is that one can login and logout.
Views need a lot of work.
|
|
|
|
|
|
|
|
| |
We're creating a minimal User model that will be filled from SSO.
We also configure Inflections so we can use SSO instead of Sso which
looks weird for a module named after an acronym.
Use Discourse as SSO: https://meta.discourse.org/t/using-discourse-as-a-sso-provider/32974
|
| |
|
| |
|
|
|