lc_alchemy_cms 3.2.0

data/.teatro.yml

@@ -0,0 +1,7 @@
+project:
+  after:
+    - apt-get -y install imagemagick
+stage:
+  before: cd spec/dummy
+  database: bin/rake db:setup RAILS_ENV=production
+  run: bin/rails server -e production

data/.travis.yml

@@ -0,0 +1,27 @@
+language: ruby
+sudo: false
+cache: bundler
+rvm:
+- 2.0.0
+- 2.1
+- 2.2.0
+branches:
+  only:
+  - master
+before_script: bundle exec rake alchemy:spec:prepare
+script: bundle exec rspec
+env:
+- DB=mysql
+- DB=postgresql
+notifications:
+  irc:
+    on_success: change
+    on_failure: always
+    use_notice: true
+    channels:
+    - irc.freenode.org#alchemy_cms
+  slack:
+    secure: QzOFw1Ph69pzwWBFgtIVkOnjbcRxB9HPRQ+RYjK+2tg+fsbiTJ+wYgHcZL49tPYcLAls4kymkFWzWBF3PCAXJMfKgUCqXzdQ2FuJC/JoVRTLll4wDnZFPG33jsm5tVznmycZ3ma4+ZWfJQ+C+elEBOba6v1kG9eGIy6sH2cvXfE=
+addons:
+  code_climate:
+    secure: qmOMqc4FUBRP25XqaYIKuxZQ/GrGLKjIc3vUqZa+XfkQKh6xLXvOF7YUM/XJZ5u6D6hk0Ly8UxjctvDY+tQxEAK49lFwK51i7bODfkQjfVBrFzfht7QhxY5HJKx7F0HHmpyNJet4n8mR0gGlhwVyXv+Tz7Rm6O3Hq3+TEbY9+pk=

data/.yardopts

@@ -0,0 +1,5 @@
+--title "Alchemy CMS"
+app/**/*.rb
+config/**/*.yml
+lib/**/*.rb
+README.md

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,13 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of AlchemyCMS, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in AlchemyCMS a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.
+
+Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+
+AlchemyCMS maintainers 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. AlchemyCMS maintainers who do not follow the Code of Conduct may be removed from the AlchemyCMS team.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the AlchemyCMS maintainers.
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/)

data/CONTRIBUTING.md

@@ -0,0 +1,73 @@
+Alchemy CMS is an open source project and we encourage contributions. Please read these
+contributors guidelines before contributing.
+
+## Filing an issue
+
+When filing an issue on the Alchemy CMS project, please provide these details:
+
+* A comprehensive list of steps to reproduce the issue.
+* What you're *expecting* to happen compared with what's *actually* happening.
+* The version of Alchemy *and* the version of Rails.
+* Your application's complete Gemfile, as text (*not as an image*)
+* Any relevant stack traces ("Full trace" preferred)
+
+In 99% of cases, this information is enough to determine the cause and solution
+to the problem that is being described.
+
+Please remember to format code using triple backticks (\`\`\`) so that it is neatly
+formatted when the issue is posted.
+
+## Pull requests
+
+We gladly accept pull requests to fix bugs and, in some circumstances, add new
+features to Alchemy.
+
+NOTE: Please discuss new features at the public Alchemy Trello board
+and/or the Alchemy discussion board, before sending a pull request.
+
+Here's a quick guide:
+
+1. Fork the repo.
+
+2. Run the tests. We only take pull requests with passing tests, and it's great
+to know that you have a clean slate:
+
+        $ bundle exec rake
+
+3. Create new branch then make changes and add tests for your changes. Only
+refactoring and documentation changes require no new tests. If you are adding
+functionality or fixing a bug, we need tests!
+
+4. Push to your fork and submit a pull request. If the changes will apply cleanly
+to the latest stable branches and master branch, you will only need to submit one
+pull request.
+
+5. If a PR does not apply cleanly to one of its targeted branches, then a separate
+PR should be created that does. For instance, if a PR applied to master & 2.7-stable but not 2.8-stable, then there should be one PR for master & 2.7-stable and another, separate PR for 2.8-stable.
+
+At this point you're waiting on us. We like to at least comment on, if not
+accept pull requests. We may suggest some changes or improvements or alternatives.
+
+Some things that will increase the chance that your pull request is accepted,
+taken straight from the Ruby on Rails guide:
+
+* Use Rails idioms and helpers
+* Include tests that fail without your code, and pass with it
+* Update the documentation, the surrounding one, examples elsewhere, guides,
+  whatever is affected by your contribution
+
+Please follow these syntax guides:
+
+* Two spaces, no tabs.
+* No trailing whitespace. Blank lines should not have any space.
+* Add a new line at the end of every file.
+* Prefer `&&`/`||` over `and`/`or`.
+* `MyClass.my_method(my_arg)` not `my_method( my_arg )` or `my_method my_arg`.
+* `a = b` and not `a=b`.
+* `a_method { |block| ... }` and not `a_method { | block | ... }`
+* Follow the conventions you see used in the source already.
+* `->` symbol over lambda
+* This `{a: 'b'}` is a hash, this `{ a + b }` is a block.
+* Ruby 1.9 hash syntax over Ruby 1.8 hash syntax
+
+And in case we didn't emphasize it enough: we love tests!

data/Gemfile

@@ -0,0 +1,34 @@
+source 'https://rubygems.org'
+
+gemspec
+
+gem 'sqlite3' if ENV['DB'].nil? || ENV['DB'] == 'sqlite'
+gem 'mysql2'  if ENV['DB'] == 'mysql'
+gem 'pg'      if ENV['DB'] == 'postgresql'
+
+group :development, :test do
+  gem 'jasmine-rails',        github: 'searls/jasmine-rails'
+  gem 'jasmine-jquery-rails', github: 'travisjeffery/jasmine-jquery-rails'
+  if ENV['TRAVIS']
+    gem "codeclimate-test-reporter", require: false
+  else
+    gem 'simplecov',                 require: false
+  end
+  unless ENV['CI']
+    gem 'launchy'
+    gem 'annotate'
+    gem 'bumpy'
+    gem 'yard'
+    gem 'redcarpet'
+    gem 'pry-byebug'
+    gem 'spring'
+    gem 'spring-commands-rspec'
+    gem 'rubocop', require: false
+  end
+end
+
+# We need this if we want to start the dummy app in production, ie on Teatro.io
+group :production do
+  gem 'uglifier', '>= 1.0.3'
+  gem 'therubyracer'
+end

data/LICENSE

@@ -0,0 +1,27 @@
+Copyright (c) 2010-2014, magic labs GmbH, Hamburg Germany
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+  Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+  Redistributions in binary form must reproduce the above copyright notice, this
+  list of conditions and the following disclaimer in the documentation and/or
+  other materials provided with the distribution.
+
+  Neither the name of the magic labs GmbH nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.md

@@ -0,0 +1,297 @@
+[![Gem Version](https://badge.fury.io/rb/alchemy_cms.svg)](http://badge.fury.io/rb/alchemy_cms)
+[![Build Status](https://travis-ci.org/AlchemyCMS/alchemy_cms.svg?branch=3.2-stable)](https://travis-ci.org/AlchemyCMS/alchemy_cms) [![Code Climate](https://codeclimate.com/github/AlchemyCMS/alchemy_cms.svg)](https://codeclimate.com/github/AlchemyCMS/alchemy_cms) [![Test Coverage](https://codeclimate.com/github/AlchemyCMS/alchemy_cms/badges/coverage.svg)](https://codeclimate.com/github/AlchemyCMS/alchemy_cms)
+
+
+## About
+
+![Alchemy CMS](http://alchemy-cms.com/assets/alchemy_logo.svg)
+
+Alchemy is a powerful, flexible and user centric Rails CMS.
+
+Read more about Alchemy on the [website](http://alchemy-cms.com) and in the [guidelines](http://guides.alchemy-cms.com).
+
+
+## Features
+
+- Highly flexible templating that completely separates content from markup
+- End-User centric graphical user interface
+- Multi language and multi domain
+- SEO friendly urls
+- User Access Control
+- Build in contact form mailer
+- Attachments and downloads
+- Powerful image rendering
+- Extendable via Rails engines
+- Integrates into existing Rails Apps
+- Flexible caching
+- Hostable on any Server that supports Ruby on Rails, a SQL Database and ImageMagick
+
+
+## Rails Version
+
+**This version of Alchemy CMS runs with Rails 4.2 only**
+
+* For a Rails 4.0/4.1 compatible version use the [`3.1-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/3.1-stable).
+* For a Rails 3.2 compatible version use the [`2.8-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/2.8-stable).
+* For a Rails 3.1 compatible version use the [`2.1-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/2.1-stable).
+* For a Rails 3.0 compatible version use the [`2.0-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/2.0-stable).
+* For a Rails 2.3 compatible version use the [`1.6-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/1.6-stable).
+
+
+## Ruby Version
+
+Alchemy runs with Ruby >= 2.0.0.
+
+For a Ruby 1.9.3 compatible version use the [`3.1-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/3.1-stable).
+
+For a Ruby 1.8.7 compatible version use the [`2.3-stable` branch](https://github.com/AlchemyCMS/alchemy_cms/tree/2.3-stable).
+
+
+## Installation
+
+### Install as a standalone project
+
+Use the installer:
+
+```shell
+$ gem install alchemy_cms
+$ alchemy new my_magicpage
+```
+
+and follow the instructions to finish the installation.
+
+The installer has some options (like choosing the database). See them with:
+
+```shell
+$ alchemy --help
+```
+
+### Install into an existing Rails project
+
+#### 1. Add the Alchemy gem:
+
+Put this into your `Gemfile`:
+
+```ruby
+gem 'alchemy_cms', github: 'AlchemyCMS/alchemy_cms', branch: '3.2-stable'
+```
+
+**NOTE:** You normally want to use a stable branch, like `3.0-stable`.
+
+If you want to use Russian translation and have better i18n support, you should put:
+
+```ruby
+gem 'russian', '~> 0.6.0'
+```
+
+or gem with similar functionality into your Gemfile.
+
+#### 2. Update your bundle:
+
+```shell
+$ bundle install
+```
+
+#### 3. Set the authentication user
+
+Now you have to decide, if you want to use your own user model or if you want to use
+the Devise based user model that Alchemy provides and was extracted [into its own gem](https://github.com/AlchemyCMS/alchemy-devise).
+
+##### Use Alchemy user
+
+If you don't have your own user class, you can use the Alchemy user model. Just add the following gem into your `Gemfile`:
+
+```ruby
+gem 'alchemy-devise', github: 'AlchemyCMS/alchemy-devise', branch: '3.2-stable'
+```
+
+**NOTE:** You normally want to use a stable branch, like `2.0-stable`.
+
+Then run:
+
+```shell
+$ bundle install
+$ bin/rake alchemy_devise:install:migrations
+```
+
+##### Use your User model
+
+In order to use your own user model you need to tell Alchemy about it.
+
+The best practice is to use an initializer:
+
+```ruby
+# config/initializers/alchemy.rb
+Alchemy.user_class_name     = 'YourUserClass'       # Defaults to 'User'
+Alchemy.current_user_method = 'current_admin_user'  # Defaults to 'current_user'
+Alchemy.signup_path         = '/your/signup/path'   # Defaults to '/signup'
+Alchemy.login_path          = '/your/login/path'    # Defaults to '/login'
+Alchemy.logout_path         = '/your/logout/path'   # Defaults to '/logout'
+```
+
+The only thing Alchemy needs to know from your user class is the `alchemy_roles` method.
+
+This method has to return an `Array` (or `ActiveRecord::Relation`) with at least one of the following roles: `member`, `author`, `editor`, `admin`.
+
+##### Example
+
+```ruby
+# app/models/user.rb
+
+def alchemy_roles
+  if admin?
+    %w(admin)
+  end
+end
+```
+
+Please follow [this guide](http://guides.alchemy-cms.com/edge/custom_authentication.html) for further instructions on how to customize your user class even more.
+
+#### 4. Install Alchemy into your app:
+
+**After** you set the user model you need to run the Alchemy install task:
+
+```shell
+$ bin/rake alchemy:install
+```
+
+Now everything should be set up and you should be able to visit the Alchemy Dashboard at:
+
+<http://localhost:3000/admin>
+
+*) Use your custom path if you mounted Alchemy at something else then `'/'`
+
+
+## Customizing
+
+Alchemy has very flexible ways to organize and manage content. Please be sure to read [the introduction guide](http://guides.alchemy-cms.com/edge/index.html) in order to understand the basic idea of how Alchemy works.
+
+
+### Custom Controllers
+
+Beginning with Alchemy 3.1 we do not patch the `ApplicationController` anymore. If you have controllers that loads Alchemy content or uses Alchemy helpers in the views (i.e. `render_navigation` or `render_elements`) you can either inherit from `Alchemy::BaseController` or you `include Alchemy::ControllerActions` in your controller (**that's the recommended way**).
+
+
+## Upgrading
+
+The Alchemy team takes upgrades very seriously and tries to make them as smooth as we can. Therefore we have build in upgrade tasks, that try to automate as much as possible.
+
+That's why after updating the Alchemy gem you should **always run the upgrader**:
+
+```shell
+$ bundle update alchemy_cms
+$ bin/rake alchemy:upgrade
+```
+
+Alchemy will print out useful information after running the automated tasks that help a smooth upgrade path. So please **take your time and read them**.
+
+Always be sure to keep an eye on the `config/alchemy/config.yml.defaults` file and update your `config/alchemy/config.yml` accordingly.
+
+Also, `git diff` is your friend. You are using git to track changes of your projects, right?
+
+
+## Deployment
+
+Alchemy has an official Capistrano extension which takes care of everything you need to deploy an Alchemy site.
+
+Please use https://github.com/AlchemyCMS/capistrano-alchemy, if you want to deploy with Capistrano.
+
+### Without Capistrano
+
+If you don't use Capistrano you have to **make sure** that the `uploads`, `tmp/cache/assets`, `public/assets` and `public/pictures` folders get **shared between deployments**, otherwise you **will loose data**. No, not really, but you know, just keep them in sync.
+
+
+## Testing
+
+If you want to contribute to Alchemy ([and we encourage you to do so](https://github.com/AlchemyCMS/alchemy_cms/blob/master/CONTRIBUTING.md)) we have a strong test suite that helps you to not break anything.
+
+### Preparation
+
+First of all you need to clone your fork to your local development machine. Then you need to install the dependencies with bundler.
+
+```shell
+$ bundle install
+```
+
+To prepare the tests of your Alchemy fork please make sure to run the preparation task:
+
+```shell
+$ bundle exec rake alchemy:spec:prepare
+```
+
+to set up the database for testing.
+
+### Run your tests with:
+
+```shell
+$ bundle exec rspec
+```
+
+**Alternatively** you can just run*:
+
+```shell
+$ bundle exec rake
+```
+
+*) This default task executes the database preparations and runs all defined test cases.
+
+### Start the dummy app
+
+You can even start the dummy app and use it to manually test your changes with:
+
+```shell
+$ cd spec/dummy
+$ bin/rake db:setup
+$ bin/rails s
+```
+
+**A note about RSpec version:**
+
+Alchemy specs are written **in RSpec 3**. Please **do not use deprecated RSpec 2.x syntax**. Thanks
+
+
+## Getting Help
+
+* Read the guidelines: http://guides.alchemy-cms.com.
+* Read the documentation: http://rubydoc.info/github/AlchemyCMS/alchemy_cms
+* If you found a bug please use the [issue tracker on Github](https://github.com/AlchemyCMS/alchemy_cms/issues).
+* For questions about general usage please use [Stack Overflow](http://stackoverflow.com/questions/tagged/alchemy-cms), [the User Group](http://groups.google.com/group/alchemy-cms) or the [IRC channel](irc://irc.freenode.net#alchemy_cms).
+* New features should be discussed on our [Trello Board](https://trello.com/alchemycms).
+
+**PLEASE** don't use the Github issues for feature requests. If you want to contribute to Alchemy please [read the contribution guidelines](https://github.com/AlchemyCMS/alchemy_cms/blob/master/CONTRIBUTING.md) before doing so.
+
+
+## Resources
+
+* Homepage: <http://alchemy-cms.com>
+* Live-Demo: <http://demo.alchemy-cms.com> (user: demo, password: demo123)
+* API Documentation: <http://rubydoc.info/github/AlchemyCMS/alchemy_cms>
+* Issue-Tracker: <https://github.com/AlchemyCMS/alchemy_cms/issues>
+* Sourcecode: <https://github.com/AlchemyCMS/alchemy_cms>
+* User Group: <http://groups.google.com/group/alchemy-cms>
+* IRC Channel: <irc://irc.freenode.net#alchemy_cms>
+* Discussion Board: <https://trello.com/alchemycms>
+* Twitter: <https://twitter.com/alchemy_cms>
+
+
+## Authors
+
+* Thomas von Deyen: <https://github.com/tvdeyen>
+* Robin Böning: <https://github.com/robinboening>
+* Marc Schettke: <https://github.com/masche842>
+* Hendrik Mans: <https://github.com/hmans>
+* Carsten Fregin: <https://github.com/cfregin>
+
+
+## License
+
+* BSD: <https://raw.github.com/magiclabs/alchemy_cms/master/LICENSE>
+
+
+## Spread the love
+
+If you like Alchemy, please help us to spread the word about Alchemy and star this repo [on GitHub](https://github.com/AlchemyCMS/alchemy_cms), upvote it [on The Ruby Toolbox](https://www.ruby-toolbox.com/projects/alchemy_cms), mention us [on Twitter](https://twitter.com/alchemy_cms) and vote for it [on Bitnami](https://bitnami.com/stack/alchemy).
+
+That will help us to keep Alchemy awesome.
+
+Thank you <3!