/markers.json
параметр | имя |
---|---|
q[business_category_id_eq] |
id категории |
q[business_sub_category_id_eq] |
id подкатегории |
Started GET "/assets/morrisjs/morris-28bfb4546f3c8d7a6455dacd000fbee8.css?body=1" for ::1 at 2015-07-18 14:17:27 +0300 | |
Started GET "/assets/bootsy-fd520f17768361ae2d1f3462aac453e1.css?body=1" for ::1 at 2015-07-18 14:17:28 +0300 | |
Started GET "/assets/admin/sb-admin-2-16a99fc1a3ed0b0f9b2cd39ef92cad34.css?body=1" for ::1 at 2015-07-18 14:17:28 +0300 | |
Started GET "/assets/shared/turbolinks-6e144842dfc112b55e4455d4d0d5db2b.css?body=1" for ::1 at 2015-07-18 14:17:28 +0300 |
30.07.2015 | |
OK.[{"Сид"=>{:tariff=>"5496", :type=>"Сид"}}, {"Купе"=>{:tariff=>"2616", :type=>"Купе"}}, {"Люкс"=>{:tariff=>"5735", :type=>"Люкс"}}, {"Мягкий"=>{:tariff=>"16617", :type=>"Мягкий"}}] | |
31.07.2015 | |
RID.RID.OK.[{"Купе"=>{:tariff=>"1546", :type=>"Купе"}}, {"Люкс"=>{:tariff=>"4880", :type=>"Люкс"}}, {"Плац"=>{:tariff=>"1387", :type=>"Плац"}}, {"Сид"=>{:tariff=>"13037", :type=>"Сид"}}, {"Мягкий"=>{:tariff=>"17694", :type=>"Мягкий"}}] | |
01.08.2015 | |
RID.RID.RID.RID.OK.[{"Люкс"=>{:tariff=>"3990", :type=>"Люкс"}}, {"Купе"=>{:tariff=>"2032", :type=>"Купе"}}, {"Плац"=>{:tariff=>"1387", :type=>"Плац"}}, {"Сид"=>{:tariff=>"3225", :type=>"Сид"}}, {"Мягкий"=>{:tariff=>"13964", :type=>"Мягкий"}}] | |
02.08.2015 | |
RID.RID.RID.OK.[{"Купе"=>{:tariff=>"2089", :type=>"Купе"}}, {"Люкс"=>{:tariff=>"4869", :type=>"Люкс"}}, {"Плац"=>{:tariff=>"1387", :type=>"Плац"}}, {"Сид"=>{:tariff=>"3870", :type=>"Сид"}}, {"Мягкий"=>{:tariff=>"14895", :type=>"Мягкий"}}] |
Measure Mode: wall_time | |
Thread ID: 70308086497800 | |
Fiber ID: 2341215640 | |
Total: 4.077675 | |
Sort by: self_time | |
%self total self wait child calls name | |
6.24 0.255 0.255 0.000 0.000 89 IO#read | |
3.70 0.151 0.151 0.000 0.000 21928 String#gsub |
paths = Dir[Rails.root.join("config/routes/**/*.rb")] | |
updater = ActiveSupport::FileUpdateChecker.new(paths) { Rails.application.routes_reloader.reload!; Rails.logger.debug('shita') } | |
Rails.application.configure do | |
config.to_prepare do | |
puts 'updated status: ' + updater.updated?.to_s | |
Rails.logger.debug('shita') | |
updater.execute_if_updated | |
end | |
end |
#= require jquery | |
#= require bootstrap | |
#= require ./application-view | |
@Modal = ApplicationView | |
getStores: -> | |
ModalStore | |
getPropsFromStores: -> |
stats_source.clicks_statistic_by(start_date..end_date, :device).tap {|arr| arr.map{|row| row[:max] = arr.max{|a, b| a[:clicks_amount] <=> b[:clicks_amount]}[:clicks_amount]}}.map{|row| row[:clicks_percentage] = 100 * row[:clicks_amount] / row[:max]; row}.each do |row| | |
print row | |
end |
#!/usr/bin/env ruby | |
require 'sprockets' | |
require 'uglifier' | |
require 'closure-compiler' | |
require "yui/compressor" | |
require 'sass-rails' | |
require 'httparty' | |
We use the Flux pattern, meaning triggering actions and reacting to state changes is done in a certain way. Calling the API and using a promise in the component isn't Flux. Your code here I'm sure works, however in a web app like ours we can quickly run into problems if we don't follow this Flux pattern. | |
For example, it's common that multiple different actions happen at once. Separate components may also be interested in the the result of an action and want to react to a state change. One or more actions may error. | |
In the jQuery/promises world web apps like ours quickly ended up in callback hell with messy chains of API calls and updates/errors. Functions got really large too. Flux is an architecture that helps us avoid that as long as we stick to some rules like: | |
components render store state and call actions (nothing else) | |
actions make API calls and update the store with the result (state) | |
components listen to the store and react to state changes | |
This lets us keep components, actions and stores small and |
Кодовое название “Хранилище” - сервис хранения данных в своем Телеграме. Как Яндекс.Диск и прочее, только файлы хранятся у вас в “Избранных сообщениях” - мы используем Телеграм как облачное хранилище.
Что нужно сделать? Дизайн Бэкенд Фронтенд
Уже есть каркас приложения на Ruby on Rails и React JS - с аутентификацией через Телеграм. Можно сделать с нуля на чем-то покруче, почему бы и нет. Желательно чтобы могло крутится на бесплатном тире Хероку - хотя согласен что это спорная идея.
Для связи с Телеграмом будем использовать https://www.t-a-a-s.ru