branding_repo 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 96873ad441e05b71a884bba825a90c4b9d3cc059029b037f22397fba312bb34f
+  data.tar.gz: d65338bbef9d4fac122cc0d435b11d24c7c33cc5621b95944058723f8f68b1e0
+SHA512:
+  metadata.gz: 8669ade2bb892590a2ef0a6b0f3b149e32b694725b9bdf587bd969e9eee1ac52284731cede4e9704e2ab051eee4e74a3eea568611d3c403c61842399272c9dd6
+  data.tar.gz: 677b1efefdda9b35cd56040c1607ace1e19c7ff9ab4ae866b71e88fc38006756f212b6b604045f97f574606a7e4de1b1e94c825df49fe64913bd98558766facf

data/.gitignore

@@ -0,0 +1,8 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/.rubocop.yml

@@ -0,0 +1,13 @@
+AllCops:
+  TargetRubyVersion: 2.4
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2021-10-22
+
+- Initial release: simple copying specified files over

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at git@murb.nl. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in branding_repo.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "minitest", "~> 5.0"
+
+gem "rubocop", "~> 1.7"

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2021 murb
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,88 @@
+# BrandingRepo (for Rails)
+
+Ever had the problem that you reuse the same project for a managemable number of clients? To few to store branding materials in a database, but more than one making it hard to keep separate branches in sync?
+
+Introducing BrandingRepo (for Rails)
+
+The idea is simple: create a configuration file with those files that are specific to different brands/customers and store their mods in a different repository. Repository is quite a big word here: we simply create a `config/brands` folder in your current branch where you can push and pull your brand specific adjustments from. All managed in the same git repository.
+
+What it is not:
+
+- it is not git within git.
+- it is not a design system, nor has it anything to do with it (I think perhaps with a few additional hacks it can be made to work with centrally managed gems/node-modules; like here: https://twitter.com/hopsoft/status/1451358882161332225?s=10)
+- it is not adding brand icons to your project
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'branding_repo'
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install branding_repo
+
+## Usage
+
+Set up a default branding:
+
+```
+$ rails branding:create default
+```
+
+This will create a `config/branding.yml` file with a list of files to copy on a brand change.
+
+It is suggested that you create a neutral 'default' brand, and make variations from it.
+
+```
+$ rails branding:push default
+```
+
+Now create a new brand:
+
+```
+$ rails branding:create org_name
+```
+
+Do your thing in making brand specific changes and push them
+
+```
+$ rails branding:push org_name
+```
+
+Before committing everything to remote, you might want to switch back to the default branch:
+
+```
+$ rails branding:pull default
+```
+
+This pull, but then for a specific brand, is also something you do just before building your image / assets.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Todo
+
+* Write some tests 😱
+* Make it work without Rails
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/branding_repo. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/branding_repo/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the BrandingRepo project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/branding_repo/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,16 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/*_test.rb"]
+end
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[test rubocop]

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "branding_repo"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/branding_repo.gemspec

@@ -0,0 +1,35 @@
+# frozen_string_literal: true
+
+require_relative "lib/branding_repo/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "branding_repo"
+  spec.version       = BrandingRepo::VERSION
+  spec.authors       = ["murb"]
+  spec.email         = ["git@murb.nl"]
+
+  spec.summary       = "Helps with manage different brandings of your Rails app in the same repo."
+  spec.description   = "Allows you to have different brandings of your app within the same repo for client a, b & c"
+  spec.homepage      = "https://murb.nl/blog?tags=branding_repo"
+  spec.license       = "MIT"
+  spec.required_ruby_version = ">= 2.4.0"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  # spec.metadata["source_code_uri"] = "TODO: Put your gem's public repo URL here."
+  # spec.metadata["changelog_uri"] = "TODO: Put your gem's CHANGELOG.md URL here."
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(File.expand_path(__dir__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+
+  # For more information and examples about making a new gem, checkout our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

data/lib/branding_repo/railtie.rb

@@ -0,0 +1,13 @@
+require 'branding_repo'
+require 'rails'
+
+module BrandingRepo
+  class Railtie < Rails::Railtie
+    railtie_name :branding_repo
+
+    rake_tasks do
+      path = File.expand_path(__dir__)
+      Dir.glob("#{path}/tasks/**/*.rake").each { |f| load f }
+    end
+  end
+end

data/lib/branding_repo/tasks/branding.rake

@@ -0,0 +1,101 @@
+BRANDING_TEMPLATE=<<TEMPLATE
+files:
+  - app/views/layouts/application.html.erb
+TEMPLATE
+
+namespace :branding do
+  desc 'create'
+  task create: :environment do
+    create_config_unless_exist!
+
+    brand_name = brand_name!(task: :create)
+
+    config = read_config
+
+    if File.exists?(Rails.root.join("config","brands", brand_name))
+      puts "Brand #{brand_name} already exists, please use rails branding:push #{brand_name}"
+      exit(1)
+    end
+
+    Dir.mkdir(Rails.root.join("config","brands", brand_name))
+
+    exit
+  end
+
+  desc 'push: update an existing brand with the current status of the brand files in the working directory'
+  task push: :environment do
+    config = read_config
+
+    brand_name = brand_name!(task: :push)
+
+    config["files"].each do |file|
+      if File.exist?(Rails.root.join(file))
+        mkdir_with_parents(File.dirname( Rails.root.join("config","brands", brand_name, file)))
+        ::FileUtils.cp(Rails.root.join(file), File.dirname(Rails.root.join("config","brands", brand_name, file)))
+      else
+        puts "Skipping #{file} ... (does not exist in current environment)"
+      end
+    end
+
+    exit
+  end
+
+  desc 'pull: update current working directory with an brand files from an existing brand'
+  task pull: :environment do
+    config = read_config
+
+    brand_name = brand_name!(task: :pull)
+
+    config["files"].each do |file|
+      if File.exist?(Rails.root.join("config","brands", brand_name, file))
+        ::FileUtils.cp(Rails.root.join("config","brands", brand_name, file), File.dirname(Rails.root.join(file)))
+      else
+        puts "Skipping #{file} ... (does not exist in brand)"
+      end
+    end
+
+    exit
+  end
+end
+
+def brand_name!(task: :taskname)
+  brand_name = ARGV[0]
+  unless brand_name
+    puts "A brand name is required: rails branding:#{task} brand_name"
+    exit(1)
+  end
+  brand_name
+end
+
+def create_config_unless_exist!
+  unless File.exist?(Rails.root.join("config","branding.yml"))
+    puts "Creating config/branding.yml as it did not exist..."
+    File.write(Rails.root.join("config","branding.yml"), BRANDING_TEMPLATE)
+  end
+  unless File.exist?(Rails.root.join("config","brands"))
+    puts "Creating config/brands as it did not exist..."
+
+    Dir.mkdir(Rails.root.join("config","brands"))
+    File.write(Rails.root.join("config","brands",".keep"),"")
+  end
+end
+
+def read_config
+  config = YAML.load(File.read(Rails.root.join("config","branding.yml")))
+  if config["files"]
+    return config
+  else
+    puts "Invalid config/branding.yml, make sure a files section exists"
+    exit(1)
+  end
+end
+
+def mkdir_with_parents(path)
+  dirname = File.dirname(path)
+  if Dir.exist?(dirname) and !Dir.exist?(path)
+    Dir.mkdir(path)
+  elsif !Dir.exist?(dirname)
+    mkdir_with_parents(dirname)
+    mkdir_with_parents(path)
+  end
+end

data/lib/branding_repo/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module BrandingRepo
+  VERSION = "0.1.0"
+end

data/lib/branding_repo.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require_relative "branding_repo/version"
+
+module BrandingRepo
+  class Error < StandardError; end
+
+  require 'branding_repo/railtie' if defined?(Rails)
+  # Your code goes here...
+end

metadata

@@ -0,0 +1,60 @@
+--- !ruby/object:Gem::Specification
+name: branding_repo
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- murb
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2021-10-22 00:00:00.000000000 Z
+dependencies: []
+description: Allows you to have different brandings of your app within the same repo
+  for client a, b & c
+email:
+- git@murb.nl
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- branding_repo.gemspec
+- lib/branding_repo.rb
+- lib/branding_repo/railtie.rb
+- lib/branding_repo/tasks/branding.rake
+- lib/branding_repo/version.rb
+homepage: https://murb.nl/blog?tags=branding_repo
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://murb.nl/blog?tags=branding_repo
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.4.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.29
+signing_key:
+specification_version: 4
+summary: Helps with manage different brandings of your Rails app in the same repo.
+test_files: []