| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
Bugfix/5549 prefer client signup
|
|
|
|
|
|
cost -> rate
quota -> storage
|
|
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.
|
|
|
|
some message tests are failing for me right now.
|
|
|
|
config/customizations in repo.
|
|
|
|
contact.
|
|
|
|
initialized constant VERIFY_PEER"
|
|
|
|
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
|
|
testing gem phantomjs-binaries)
|
|
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
|
|
Bugfix/4703 disable unsupported settings
|
|
with tests
|
|
* in case the user has a session id, keep it but proceed without a session
* in case we can't initialize the models proceed
* if APP_CONFIG[:reraise_errors] is set we'll crash instead in the latter case
default to reraise errors in dev and test environments.
|
|
service level code won't break anything if it isn't set in the config.
|
|
* stores desired & effective service level
* whenever desired level is changed, effective level will be updated
* allows user to set their desired service level
* allow admin to update desired & effective service level
|
|
|
|
time a rake task is run (especially since some rake tasks get run as root!)
|
|
|
|
|
|
|
|
They did not point directly to the download.
|
|
|
|
This way we won't have to redeploy once the new links to the windows and the android version are there.
Also this obviously offers more flexibility for providers.
|
|
We blacklist based on three things:
* blacklist in APP_CONFIG[:handle_blacklist]
* emails in RFC 2142
* usernames in /etc/passwd
The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist].
We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry.
|
|
log_tags was causing errors that could not be logged or caught. We don't
need them yet anyway.
config.log_tags accepts a list of methods that respond to request
object. This makes it easy to tag log lines with debug information like
subdomain and request id — both very helpful in debugging multi-user
production applications.
http://guides.rubyonrails.org/configuring.html
|
|
This reverts commit 073dc636ffa2da07ee7a719c6166a3ca1b593fb3.
Conflicts:
config/environments/production.rb
|
|
also make sure the gem > 2.0.0 so it actually IS called Syslog::Logger.
|
|
Feature/sessions expire
|
|
|
|
|
|
|
|
|
|
This is the most simple thing that could possibly work.
If you do not specify a :logfile in your environments config Rails will use the default.
|
|
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.
|
|
Conflicts:
app/views/home/index.html.haml
|
