| Age | Commit message (Collapse) | Author |
|---|
|
keeping the platform detection for now.
|
|
To use bitmask services:
Download Bitmask
|
|
|
|
The client_side_validations gem is not maintained anymore and the validations
were not working lately. So instead of trying to fix it I started working on
independent validations for the password as it can't be validated on the
server due to SRP.
So far these validations are very primitive. They require 8 characters length
and a matching confirmation.
|
|
|
|
the loading... text on the buttons was not capitalized before.
So in order to change this in a (more or less) single place i added
new button types to simple_form:
button :wrapped - normal button, with loading and an optional cancel button wrapped in the classical bootstrap action div.
cancel option contains the url to go to when canceling.
button :loading - simple button with loading text capitalized by using i18n (simple_form.buttons.loading)
Conflicts:
engines/support/app/views/tickets/new.html.haml
|
|
Feature/api quota support + current_user null pattern
|
|
let's devide the partials rather than having super specific parameters (on_user_page)
|
|
|
|
cost -> rate
quota -> storage
|
|
if neither limited nor unlimited certs are allowed there will be no prefix. Not sure if this is desired - but it's the way things used to be before the refactoring
|
|
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors.
So instead we still use the allow_..._certs and ..._cert_prefix options.
They basically provide the framework in which service levels can operate.
The service level configuration will not include the cert prefix anymore.
It only states if the service level is rate limited or not.
This avoids conflicts between the two configuration options.
I also removed the anonymous service level entirely.
It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in.
Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
|
|
Null Pattern for current_user - use it to get rid of some conditionals
|
|
this still allows us to do current_user.service_level.
Have not gone through the rest of the code yet.
Only made sure logged_in? now tests for is_a? User instead of !!current_user
|
|
:api/service will return a hash of the current users service level
This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
|
|
|
|
cleaned up all the engine stuff that was never really used.
Afterwards there is not that much left that makes it into the toplevel.
|
|
|
|
|
|
|
|
(not linux32 or linux64).
|
|
|
|
flexible.
|
|
contact.
|
|
|
|
|
|
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
|
|
* set locale based on request header
* enforce locale path prefix when current locale is not the default
* note: don't use root_path anymore, instead use home_path
|
|
|
|
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
|
|
Conflicts:
billing/config/locales/en.yml
|
|
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller.
This also simplifies linking to the users in question a lot.
|
|
|
|
Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well.
|
|
|
|
|
|
Feature/billing past due subscriptions
|
|
We add a class to the html element based on the detected os and use that to pick which download link should be visible.
If we detect an os that is not supported we display a deactivated download link instead with all alternatives.
|
|
customer in any way.
|
|
|
|
Normally rails sends an html page which can't be parsed by the client.
|
|
identities controller will replace it.
|
|
specify which gems for which environments.
Here, we have the billing gem included for the development and test environments only, hardcoded in the Gemfile.
Then we show the links to billing based on a config file setting. The setting itself could be used to specify different types of billing, but isn't yet.
|
|
|
|
disable, must remove billing engine from Gemfile (and re-bundle)
|
|
Feature/identity rewrite
|
|
|
|
Conflicts:
app/views/home/index.html.haml
|
|
|
|
customer.
|
