developer toolbox » ruby » rails

preslušao ovu konferenciju, odlična prezentacija

http://aac2009.confreaks.com/07-feb-2009-10-00-browsercms-patrick-peak-and-paul-barry.html

http://www.browsercms.org/

licenca: GPLV3

BrowserCMS is intended to offer features comparable to commercial CMS products, which can support larger teams of editors. This means having a robust set of features as part of its core, as well as the capability to customize it via modules.

• It's just Rails: Each CMS project is a rails project that depends on the BrowserCMS gem. Developers can add new controllers, views, etc; just like any rails project.
• Direct in context editing: Users can browse their site to locate content and change it right on the page itself.
• Design friendly Templates: Pages aren't just a template and giant single chunk of HTML. Templates can be built to have multiple editable areas, to allow for rich designs that are still easy to manage by non-technical users.
• Sitemap: An explorer/finder style view of sections and pages in a site allowing users to add and organize pages.
• Content Library: Provides a standardized 'CRUD' interface to allow users to manage both core and custom content types.
• Content API: A set of behaviors added to ActiveRecord which allow for versioning, auditing, tagging and other content services provided by the CMS.
• Section Based Security: Admins can control which users can access specific sections (public users), as well as who can edit which pages (cms users).
• Workflow: Supports larger website teams where some users can contribute, but not publish. Users can assign work to other publishers to review.
• Page Caching: Full page caching allows the web server (Apache) to serve HTML statically when they don't change.

prvo sam pokušavao ovo uraditi sa 2.3.3 rails-om ali mi je ispadao na rake db:migrate

greška je bila wrong number of arguments, sanitize_sql

nešto slično se ovdje prijavljuje http://railsforum.com/viewtopic.php?id=33145

Chef cookbooks for BrowserCMS

bringout@nmraka-2:~/devel/git/upstream/browsercms$ git push gitorious master --tags

Counting objects: 19866, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (7360/7360), done.
Writing objects: 100% (19866/19866), 7.95 MiB | 3853 KiB/s, done.
Total 19866 (delta 11343), reused 19866 (delta 11343)
=> Syncing Gitorious... [OK]
To git@gitorious.bring.out.ba:browsercms/browsercms.git
 * [new branch]      master -> master
 * [new tag]         v3.0.0 -> v3.0.0
 * [new tag]         v3.0.1 -> v3.0.1
 * [new tag]         v3.0.2 -> v3.0.2

http://groups.google.com/group/browsercms/browse_thread/thread/56879120114f0321

Here's my short version, non-legally binding interpretation.

BrowserCMS is LGPL. Basically, you can use BrowserCMS for open source
and commercial products, without needing to alter the license of your
code. If you make modifications to the source code of BrowserCMS, and
redistribute that altered code, you need to LGPL the altered code.

Our intent is to allow developers/designers to be able to create both
open source and commercial modules and themes, and do pretty much
whatever they want with them. We just want to protect the core of the
system to make sure it remains open source.

započeo raditi developer guide