Rails is a web-application framework that includes everything needed to create
database-backed web applications according to the Model-View-Controller (MVC)
pattern.
Understanding the MVC pattern is key to understanding Rails. MVC divides your
application into three layers: Model, View, and Controller, each with a specific
responsibility.
Active Record, Active Model, Action Pack, and Action View can each be used
independently outside Rails.
In addition to that, Rails also comes with:
- Action Mailer, a library to generate and send emails
- Action Mailbox, a library to receive emails within a Rails application
- Active Job, a framework for declaring jobs and making them run on a variety of
queuing backends
- Action Cable, a framework to integrate WebSockets with a Rails application
- Active Storage, a library to attach cloud and local files to Rails
applications
- Action Text, a library to handle rich text content
- Active Support, a collection of utility classes and standard library
extensions that are useful for Rails, and may also be used independently
outside Rails
===> The following configuration options are available for rubygem-rails4-4.2.11.3:
MEMCACHE_CLIENT=off: MemCache-Client support
===> Use 'make config' to modify these settings
devel/ruby-gems: Update to 3.5.6
While here, mark textproc/rubygem-nokogumbo as BROKEN because build
fails with clean latest ports tree and all supported ruby versions.
ChangeLog: https://github.com/rubygems/rubygems/blob/v3.5.6/CHANGELOG.md
PR: 276884
Approved by: sunpoet (ruby@, maintainer)
Exp-run by: antoine
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D37925
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
www: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
*
* <hvo.pm@xs4all.nl>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron LI <aly@aaronly.me>
* Aaron Zauner <az_mail@gmx.at>
* Abel Chow <achow@transoft.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Adrian Steinmann <ast@marabu.ch>
* Akinori MUSHA aka knu <knu@idaemons.org>
(Only the first 15 lines of the commit message are shown above )
devel/ruby-gems: Update to 3.3.7
These are fixes Ruby 3.0
Changes were compiled against all dependencies of devel/ruby-gems and
they all built cleanly.
There are five known build failures, all prexisting:
* devel/rubygem-xdg5: requires Ruby 3.0
* devel/rubygem-xdg: requires Ruby 3.1
* graphics/rubygem-objectdetect: port explicitly marked broken
* mail/rubygem-tmail: port explicitly marked broken
* science/cdcl: marked broken, unfetchable
Plus, science/rubygem-ruby-dcl gets skipped because of science/cdcl
PR: 258108
Approved by: ruby (zi@)
Fix PASSENGER_RUN_DEPENDS
dvl@ introduced the FLAVOR support to www/rubygem-passenger in r459684 which
adds PKGNAMESUFFIX.
PR: 225465
Reported by: Daniel Ylitalo <daniel@blodan.se>
www/rubygem-rails4: use correct deps
Use correct versions of rubygem-coffee-rails and rubygem-web-console which
allows "rails new appname" to run without installing additional gems.
Change all occurrences of xmj@chaot.net to johannes@perceivon.net as the owner
requested.
This only affects "Created by" lines with one exception: devel/uclcmd. There the
maintainer is changed. This was overlooked in r416918.
Approved by: junovitch (mentor)
create USES=gem and update rubygem- ports to use it
Note that for now ports still have to have USE_RUBY=yes to use USES=gem
PR: 209041
Differential Revision: https://reviews.freebsd.org/D6070
Remove UNIQUENAME and LATEST_LINK.
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
www/rubygem-rails4: create port for rails4
This port required creating a number of new ports, old versions of existing
ports and other adjustments, so do all that while here too.
Rails is a web-application framework for the MVC pattern that includes
both a template engine, controller framework, and object-relational
mapping package. Everything needed to develop web-apps that can run on
CGI, FastCGI, and mod_ruby
Being a full-stack framework means that all layers are built to work
seamlessly together. That way you Don't Repeat Yourself (DRY) and you
can use a single language from top to bottom. Everything from templates
to control flow to business logic is written in Ruby - The language of
love for industry heavy-weights.
WWW: http://www.rubyonrails.org
Submitted by: xmj (based on)