| module NerdNode | |
| # Rack app to reject common bot attacks. Returns a random HTTP status and content type, along with some LOLs. | |
| # | |
| # Usage: | |
| # use NerdNode::BotProtector, /phpmyadmin\/scripts|mysql\/scripts/ | |
| # | |
| # # ...or use the Regexp helper which takes an array of URL strings... | |
| # blacklist = BotProtector.build_regex(['phpmyadmin/scripts', 'mysql/scripts']) | |
| # use NerdNode::BotProtector, blacklist | |
| # |
| module ActiveRecord | |
| module ApplicationName | |
| def self.included(base) | |
| unless base.respond_to? :establish_connection_with_application_name | |
| base.extend ClassMethods | |
| base.class_eval do | |
| class << self | |
| alias_method_chain :establish_connection, :application_name | |
| end | |
| end |
| # This is a skeleton for testing models including examples of validations, callbacks, | |
| # scopes, instance & class methods, associations, and more. | |
| # Pick and choose what you want, as all models don't NEED to be tested at this depth. | |
| # | |
| # I'm always eager to hear new tips & suggestions as I'm still new to testing, | |
| # so if you have any, please share! | |
| # | |
| # @kyletcarlson | |
| # | |
| # This skeleton also assumes you're using the following gems: |
| require 'net/http' | |
| require 'json' | |
| require 'uri' | |
| @token = '' | |
| def list_files | |
| ts_to = (Time.now - 30 * 24 * 60 * 60).to_i # 30 days ago | |
| params = { | |
| token: @token, |
| AllCops: | |
| RunRailsCops: true | |
| Documentation: | |
| Enabled: false | |
| Style/AlignHash: | |
| Enabled: false | |
| Style/AlignParameters: |
The goal is to support soft delete functionality in Ecto.Repo. With the suggestion by @imranismail, another repo is created and the remaining functionalities are delegate to the original MyApp.Repo.
The new repo get/2 and all/1 functions will exclude the soft deleted record by default. delete/1 and delete_all/1 will update the delete_at column by default instead of deleting.
MyApp.Repo.get(MyApp.User, 1) //will return nil if record is in soft delete state
| defmodule Ot.Mixfile do | |
| use Mix.Project | |
| def project do | |
| [app: :ot, | |
| version: "0.1.0", | |
| elixir: "~> 1.4", | |
| build_embedded: Mix.env == :prod, | |
| start_permanent: Mix.env == :prod, | |
| deps: deps()] |
| FROM elixir:1.4.5 as asset-builder-mix-getter | |
| ENV HOME=/opt/app | |
| RUN mix do local.hex --force, local.rebar --force | |
| # Cache elixir deps | |
| COPY config/ $HOME/config/ | |
| COPY mix.exs mix.lock $HOME/ | |
| COPY apps/myproject_web/mix.exs $HOME/apps/myproject_web/ | |
| COPY apps/myproject_web/config/ $HOME/apps/myproject_web/config/ |
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).