gemstash 1.0.0.pre.1-java → 2.5.0-java

data/lib/gemstash/man/gemstash-mirror.7.txt

@@ -0,0 +1,31 @@
+4mgemstash-mirror24m(7) 					 4mgemstash-mirror24m(7)
+
+<!-- Automatically generated by Pandoc -->
+
+1mUsing Gemstash as a Mirror0m
+       If you don't have control over your Gemfile, or you don't want to force
+       everyone  on  your  team to go through the Gemstash server, you can use
+       Bundler mirroring to bundle against your Gemstash server.
+
+       For each source in your Gemfile, add a mirror pointing to your Gemstash
+       server:
+
+	      $ bundle config mirror.http://rubygems.org http://localhost:9292
+	      $ bundle config mirror.https://my.gem-source.local http://localhost:9292/upstream/$(ruby -rcgi -e 'puts CGI.escape("https://my.gem-source.local")')
+
+       From now on, bundler will fetch gems from those sources via  your  Gem-
+       stash server.
+
+1mSimpler Gemstash Mirrors0m
+       1mThis feature requires Bundler to be at least version 1.11.0.0m
+
+       If  you	are using Bundler version 1.11.0 or greater, the mirroring be-
+       comes a bit easier:
+
+	      $ bundle config mirror.http://rubygems.org http://localhost:9292
+	      $ bundle config mirror.https://my.gem-source.local http://localhost:9292
+
+       Bundler will then send headers to Gemstash to indicate the correct  up-
+       stream.
+
+			       October 25, 2015 	    4mgemstash-mirror24m(7)

data/lib/gemstash/man/gemstash-multiple-sources.7

@@ -0,0 +1,131 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-multiple-sources" "7" "October 8, 2015" "" ""
+.SH Multiple Gem Sources
+Gemstash will stash from any amount of gem sources.
+By the end of this guide, you will be able to bundle using multiple gem
+sources, all stashed within your Gemstash server.
+.SS Default Source
+When you don\[cq]t provide an explicit source (as with the Quickstart
+Guide), your gems will be fetched from https://rubygems.org.
+This default source is not set in stone.
+To change it, you need only edit the Gemstash configuration found at
+\f[CR]\[ti]/.gemstash/config.yml\f[R]:
+.IP
+.EX
+# \[ti]/.gemstash/config.yml
+---
+:rubygems_url: https://my.gem-source.local
+.EE
+.PP
+Make sure to restart your Gemstash server after changing the config:
+.IP
+.EX
+$ gemstash stop
+$ gemstash start
+.EE
+.PP
+Once restarted, bundling against \f[CR]http://localhost:9292\f[R] will
+fetch gems from \f[CR]https://my.gem-source.local\f[R].
+If you had bundled before making these changes, fear not; bundling with
+a different default gem source will store gems in a separate location,
+ensuring different sources won\[cq]t leak between each other.
+.SS Bundling with Multiple Sources
+Changing the default source won\[cq]t help you if you need to bundle
+against https://rubygems.org along with additional sources.
+If you need to bundle with multiple gem sources, Gemstash doesn\[cq]t
+need to be specially configured.
+Your Gemstash server will honor any gem source specified via a
+specialized URL.
+Consider the following \f[CR]Gemfile\f[R]:
+.IP
+.EX
+# ./Gemfile
+require \[dq]cgi\[dq]
+source \[dq]http://localhost:9292\[dq]
+gem \[dq]rubywarrior\[dq]
+
+source \[dq]http://localhost:9292/upstream/#{CGI.escape(\[dq]https://my.gem-source.local\[dq])}\[dq] do
+  gem \[dq]my-gem\[dq]
+end
+
+source \[dq]http://localhost:9292/upstream/my-other.gem-source.local\[dq] do
+  gem \[dq]my-other-gem\[dq]
+end
+.EE
+.PP
+Notice the \f[CR]CGI.escape\f[R] call in the second source.
+This is important, as it properly URL escapes the source URL so Gemstash
+knows what gem source you want.
+The \f[CR]/upstream\f[R] prefix tells Gemstash to use a gem source other
+than the default source.
+You can now bundle with the additional source.
+.PP
+Notice that the third source doesn\[cq]t need to be escaped.
+This is because the \f[CR]https://\f[R] is used by default when no
+scheme is set, and the source URL does not contain any characters that
+need to be escaped.
+.SS Authentication with Multiple Sources
+You can use basic authentication or API keys on sources directly in
+Gemfile or using ENV variables on the Gemstash instance.
+.PP
+Example \f[CR]Gemfile\f[R]:
+.IP
+.EX
+# ./Gemfile
+require \[dq]cgi\[dq]
+source \[dq]http://localhost:9292\[dq]
+
+source \[dq]http://localhost:9292/upstream/#{CGI.escape(\[dq]user:password\[at]my.gem-source.local\[dq])}\[dq] do
+  gem \[dq]my-gem\[dq]
+end
+
+source \[dq]http://localhost:9292/upstream/#{CGI.escape(\[dq]api_key\[at]my-other.gem-source.local\[dq])}\[dq] do
+  gem \[dq]my-other-gem\[dq]
+end
+.EE
+.PP
+If you set \f[CR]GEMSTASH_<HOST>\f[R] ENV variable with your
+authentication information, you can omit it from the \f[CR]Gemfile\f[R]:
+.IP
+.EX
+# ./Gemfile
+source \[dq]http://localhost:9292\[dq]
+
+source \[dq]http://localhost:9292/upstream/my.gem-source.local\[dq] do
+  gem \[dq]my-gem\[dq]
+end
+.EE
+.PP
+And run the Gemstash with the credentials set in an ENV variable:
+.IP
+.EX
+GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --no-daemonize --config-file config.yml.erb
+.EE
+.PP
+The name of the ENV variable is the uppercase version of the host name,
+with all \f[CR].\f[R] characters replaced with \f[CR]__\f[R], all
+\f[CR]-\f[R] with \f[CR]___\f[R] and a \f[CR]GEMSTASH_\f[R] prefix (it
+uses the same syntax as
+Bundler (https://bundler.io/v2.4/man/bundle-config.1.html#CREDENTIALS-FOR-GEM-SOURCES)).
+.PP
+Example: \f[CR]my.gem-source.local\f[R] =>
+\f[CR]GEMSTASH_MY__GEM___SOURCE__LOCAL\f[R]
+.SS Redirecting
+Gemstash supports an alternate mode of specifying your gem sources.
+If you want Gemstash to redirect Bundler to your given gem sources, then
+you can specify your \f[CR]Gemfile\f[R] like so:
+.IP
+.EX
+# ./Gemfile
+require \[dq]cgi\[dq]
+source \[dq]http://localhost:9292/redirect/#{CGI.escape(\[dq]https://rubygems.org\[dq])}\[dq]
+gem \[dq]rubywarrior\[dq]
+.EE
+.PP
+Notice the \f[CR]/redirect\f[R] prefix.
+This prefix tells Gemstash to redirect API calls to the provided URL.
+Redirected calls like this will not be cached by Gemstash, and gem files
+will not be stashed, even if they were previously cached or stashed from
+the same gem source.

data/lib/gemstash/man/gemstash-multiple-sources.7.txt

@@ -0,0 +1,116 @@
+4mgemstash-multiple-sources24m(7)		       4mgemstash-multiple-sources24m(7)
+
+<!-- Automatically generated by Pandoc -->
+
+1mMultiple Gem Sources0m
+       Gemstash will stash from any amount of gem sources.  By the end of this
+       guide,  you  will  be  able  to	bundle using multiple gem sources, all
+       stashed within your Gemstash server.
+
+   1mDefault Source0m
+       When you don't provide an  explicit  source  (as  with  the  Quickstart
+       Guide),	your gems will be fetched from https://rubygems.org.  This de-
+       fault source is not set in stone.  To change it, you need only edit the
+       Gemstash configuration found at ~/.gemstash/config.yml:
+
+	      # ~/.gemstash/config.yml
+	      ---
+	      :rubygems_url: https://my.gem-source.local
+
+       Make sure to restart your Gemstash server after changing the config:
+
+	      $ gemstash stop
+	      $ gemstash start
+
+       Once restarted, bundling against http://localhost:9292 will fetch  gems
+       from  https://my.gem-source.local.   If	you  had bundled before making
+       these changes, fear not; bundling with a different default  gem	source
+       will  store  gems  in  a  separate location, ensuring different sources
+       won't leak between each other.
+
+   1mBundling with Multiple Sources0m
+       Changing the default source won't  help	you  if  you  need  to	bundle
+       against	https://rubygems.org  along  with  additional sources.	If you
+       need to bundle with multiple gem sources, Gemstash doesn't need	to  be
+       specially  configured.	Your Gemstash server will honor any gem source
+       specified via a specialized URL.  Consider the following Gemfile:
+
+	      # ./Gemfile
+	      require "cgi"
+	      source "http://localhost:9292"
+	      gem "rubywarrior"
+
+	      source "http://localhost:9292/upstream/#{CGI.escape("https://my.gem-source.local")}" do
+		gem "my-gem"
+	      end
+
+	      source "http://localhost:9292/upstream/my-other.gem-source.local" do
+		gem "my-other-gem"
+	      end
+
+       Notice the CGI.escape call in the second source.  This is important, as
+       it properly URL escapes the source  URL	so  Gemstash  knows  what  gem
+       source  you  want.   The  /upstream  prefix tells Gemstash to use a gem
+       source other than the default source.  You can now bundle with the  ad-
+       ditional source.
+
+       Notice  that  the third source doesn't need to be escaped.  This is be-
+       cause the https:// is used by default when no scheme is	set,  and  the
+       source URL does not contain any characters that need to be escaped.
+
+   1mAuthentication with Multiple Sources0m
+       You  can  use  basic  authentication or API keys on sources directly in
+       Gemfile or using ENV variables on the Gemstash instance.
+
+       Example Gemfile:
+
+	      # ./Gemfile
+	      require "cgi"
+	      source "http://localhost:9292"
+
+	      source "http://localhost:9292/upstream/#{CGI.escape("user:password@my.gem-source.local")}" do
+		gem "my-gem"
+	      end
+
+	      source "http://localhost:9292/upstream/#{CGI.escape("api_key@my-other.gem-source.local")}" do
+		gem "my-other-gem"
+	      end
+
+       If you set GEMSTASH_<HOST> ENV variable with your authentication infor-
+       mation, you can omit it from the Gemfile:
+
+	      # ./Gemfile
+	      source "http://localhost:9292"
+
+	      source "http://localhost:9292/upstream/my.gem-source.local" do
+		gem "my-gem"
+	      end
+
+       And run the Gemstash with the credentials set in an ENV variable:
+
+	      GEMSTASH_MY__GEM___SOURCE__LOCAL=user:password gemstash start --no-daemonize --config-file config.yml.erb
+
+       The name of the ENV variable is the uppercase version of the host name,
+       with all . characters replaced with __, all - with ___ and a  GEMSTASH_
+       prefix	   (it	   uses     the     same     syntax	as     Bundler
+       (https://bundler.io/v2.4/man/bundle-config.1.html#CREDENTIALS-FOR-GEM-
+       SOURCES)).
+
+       Example: my.gem-source.local => GEMSTASH_MY__GEM___SOURCE__LOCAL
+
+   1mRedirecting0m
+       Gemstash supports an alternate mode of specifying your gem sources.  If
+       you want Gemstash to redirect Bundler to your given gem	sources,  then
+       you can specify your Gemfile like so:
+
+	      # ./Gemfile
+	      require "cgi"
+	      source "http://localhost:9292/redirect/#{CGI.escape("https://rubygems.org")}"
+	      gem "rubywarrior"
+
+       Notice  the  /redirect  prefix.	This prefix tells Gemstash to redirect
+       API calls to the provided URL.  Redirected calls like this will not  be
+       cached  by  Gemstash,  and  gem files will not be stashed, even if they
+       were previously cached or stashed from the same gem source.
+
+				October 8, 2015   4mgemstash-multiple-sources24m(7)

data/lib/gemstash/man/gemstash-private-gems.7

@@ -0,0 +1,191 @@
+<!-- Automatically generated by Pandoc -->
+.\" Automatically generated by Pandoc 3.1.8
+.\"
+.TH "gemstash-private-gems" "7" "October 8, 2015" "" ""
+.SH Private Gems
+Stashing private gems in your Gemstash server requires a bit of
+additional setup.
+If you haven\[cq]t read through the Quickstart Guide, you should do that
+first.
+By the end of this guide, you will be able to interact with your
+Gemstash server to store and retrieve your private gems.
+.SS Authorizing
+\f[B]IMPORTANT NOTE:\f[R] Do not use the actual key value in this
+document, otherwise your Gemstash server will be vulnerable to anyone
+who wants to try to use the key against your server.
+Instead of the key value here, use whatever key is generated from
+running the commands.
+.PP
+In order to push a gem to your Gemstash server, you need to first create
+an API key.
+Utilize the \f[CR]gemstash authorize\f[R] command to create the API key:
+.IP
+.EX
+$ gemstash authorize
+Your new key is: e374e237fdf5fa5718d2a21bd63dc911
+.EE
+.PP
+This new key can \f[CR]push\f[R], \f[CR]yank\f[R], and \f[CR]fetch\f[R]
+gems from your Gemstash server.
+Run \f[CR]gemstash authorize\f[R] with just the permissions you want to
+limit what the key will be allowed to do.
+You can similarly update a specific key by providing it via the
+\f[CR]--key\f[R] option:
+.IP
+.EX
+$ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
+.EE
+.PP
+When no permissions are provided (like the first example), the key will
+be authorized for all permissions.
+Leave the key authorized with everything if you want to use it to try
+all private gem interactions:
+.IP
+.EX
+$ gemstash authorize --key e374e237fdf5fa5718d2a21bd63dc911
+.EE
+.PP
+With the key generated, you\[cq]ll need to tell Rubygems about your new
+key.
+If you\[cq]ve pushed a gem to https://rubygems.org, then you will
+already have a credentials file to add the key to.
+If not, run the following commands before modifying the credentials
+file:
+.IP
+.EX
+$ mkdir -p \[ti]/.gem
+$ touch \[ti]/.gem/credentials
+$ chmod 0600 \[ti]/.gem/credentials
+.EE
+.PP
+Add your new key to credentials such that it looks something like this
+(but make sure not to remove any existing keys):
+.IP
+.EX
+# \[ti]/.gem/credentials
+---
+:test_key: e374e237fdf5fa5718d2a21bd63dc911
+.EE
+.PP
+The name \f[CR]test_key\f[R] can be anything you want, but you will need
+to remember it and use it again later in this guide for the
+\f[CR]--key\f[R] option.
+.SS Creating a Test Gem
+You\[cq]ll need a test gem before you can play with private gems on your
+Gemstash server.
+If you have a gem you can use, move along to the next section.
+You can start by instantiating a test gem via Bundler:
+.IP
+.EX
+$ bundle gem private-example
+.EE
+.PP
+You\[cq]ll need to add a summary and description to the new gem\[cq]s
+gemspec file in order to successfully build it.
+Once you\[cq]ve built the gem, you will be ready to push the new gem.
+.IP
+.EX
+$ cd private-example
+$ rake build
+.EE
+.PP
+You will now have a gem at
+\f[CR]private-example/pkg/private-example-0.1.0.gem\f[R].
+.SS Pushing
+If your Gemstash server isn\[cq]t running, go ahead and start it:
+.IP
+.EX
+$ gemstash start
+.EE
+.PP
+Push your test gem using Rubygems:
+.IP
+.EX
+$ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
+.EE
+.PP
+The \f[CR]/private\f[R] portion of the \f[CR]--host\f[R] option tells
+Gemstash you are interacting with the private gems.
+Gemstash will not let you push, or yank from anything except
+\f[CR]/private\f[R].
+.SS Bundling
+Once your gem is pushed to your Gemstash server, you are ready to bundle
+it.
+Create a \f[CR]Gemfile\f[R] and specify the gem.
+You will probably want to wrap the private gem in a source block, and
+let the rest of Gemstash handle all other gems:
+.IP
+.EX
+# ./Gemfile
+source \[dq]http://localhost:9292\[dq]
+gem \[dq]rubywarrior\[dq]
+
+source \[dq]http://localhost:9292/private\[dq] do
+  gem \[dq]private-example\[dq]
+end
+.EE
+.PP
+Notice that the Gemstash server points to \f[CR]/private\f[R] again when
+installing your private gem.
+Go ahead and bundle to install your new private gem:
+.IP
+.EX
+$ bundle
+.EE
+.SS Yanking
+If you push a private gem by accident, you can yank the gem with
+Rubygems:
+.IP
+.EX
+$ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
+.EE
+.PP
+Like with pushing, the \f[CR]/private\f[R] portion of the host option
+tells Gemstash you are interacting with private gems.
+Gemstash will only let you yank from \f[CR]/private\f[R].
+Unlike pushing, Rubygems doesn\[cq]t support \f[CR]--host\f[R] for yank
+(yet), so you need to specify the host via the \f[CR]RUBYGEMS_HOST\f[R]
+environment variable.
+.SS Protected Fetching
+By default, private gems and specs can be accessed without
+authentication.
+.PP
+Private gems often require protected fetching.
+For backwards compatibility this is disabled by default, but can be
+enabled via \f[CR]$ gemstash setup\f[R] command.
+.PP
+When protected fetching is enabled API keys with the permissions
+\f[CR]all\f[R] or \f[CR]fetch\f[R] can be used to download gems and
+specs.
+.PP
+On the Bundler side, there are a few ways to configure credentials for a
+given gem source:
+.PP
+Add credentials globally:
+.IP
+.EX
+$ bundle config my-gemstash.dev api_key
+.EE
+.PP
+Add credentials in Gemfile:
+.IP
+.EX
+source \[dq]https://api_key\[at]my-gemstash.dev\[dq]
+.EE
+.PP
+However, it\[cq]s not a good practice to commit credentials to source
+control.
+A recommended solution is to use Bundler\[cq]s configuration
+keys (http://bundler.io/man/bundle-config.1.html#CONFIGURATION-KEYS),
+e.g.:
+.IP
+.EX
+$ export BUNDLE_MYGEMSTASH__DEV=api_key
+.EE
+.PP
+Behind the scene, Bundler will pick up the ENV var according to the host
+name (e.g.\ mygemstash.dev) and add to \f[CR]URI.userinfo\f[R] for
+making requests.
+.PP
+The API key is treated as a HTTP Basic Auth username and any HTTP Basic
+password supplied will be ignored.

data/lib/gemstash/man/gemstash-private-gems.7.txt

@@ -0,0 +1,154 @@
+4mgemstash-private-gems24m(7)				   4mgemstash-private-gems24m(7)
+
+<!-- Automatically generated by Pandoc -->
+
+1mPrivate Gems0m
+       Stashing  private  gems in your Gemstash server requires a bit of addi-
+       tional setup.  If you haven't read through the  Quickstart  Guide,  you
+       should  do  that  first.  By the end of this guide, you will be able to
+       interact with your Gemstash server to store and retrieve  your  private
+       gems.
+
+   1mAuthorizing0m
+       1mIMPORTANT  NOTE: 22mDo not use the actual key value in this document, oth-
+       erwise your Gemstash server will be vulnerable to anyone who  wants  to
+       try to use the key against your server.	Instead of the key value here,
+       use whatever key is generated from running the commands.
+
+       In  order to push a gem to your Gemstash server, you need to first cre-
+       ate an API key.	Utilize the gemstash authorize command to  create  the
+       API key:
+
+	      $ gemstash authorize
+	      Your new key is: e374e237fdf5fa5718d2a21bd63dc911
+
+       This  new key can push, yank, and fetch gems from your Gemstash server.
+       Run gemstash authorize with just the permissions you want to limit what
+       the key will be allowed to do.  You can similarly update a specific key
+       by providing it via the --key option:
+
+	      $ gemstash authorize push yank --key e374e237fdf5fa5718d2a21bd63dc911
+
+       When no permissions are provided (like the first example), the key will
+       be authorized for all  permissions.   Leave  the  key  authorized  with
+       everything if you want to use it to try all private gem interactions:
+
+	      $ gemstash authorize --key e374e237fdf5fa5718d2a21bd63dc911
+
+       With  the  key  generated,  you'll need to tell Rubygems about your new
+       key.  If you've pushed a gem to https://rubygems.org, then you will al-
+       ready have a credentials file to add the key to.  If not, run the  fol-
+       lowing commands before modifying the credentials file:
+
+	      $ mkdir -p ~/.gem
+	      $ touch ~/.gem/credentials
+	      $ chmod 0600 ~/.gem/credentials
+
+       Add  your new key to credentials such that it looks something like this
+       (but make sure not to remove any existing keys):
+
+	      # ~/.gem/credentials
+	      ---
+	      :test_key: e374e237fdf5fa5718d2a21bd63dc911
+
+       The name test_key can be anything you want, but you will need to remem-
+       ber it and use it again later in this guide for the --key option.
+
+   1mCreating a Test Gem0m
+       You'll need a test gem before you can play with private	gems  on  your
+       Gemstash server.  If you have a gem you can use, move along to the next
+       section.  You can start by instantiating a test gem via Bundler:
+
+	      $ bundle gem private-example
+
+       You'll  need  to add a summary and description to the new gem's gemspec
+       file in order to successfully build it.	Once you've built the gem, you
+       will be ready to push the new gem.
+
+	      $ cd private-example
+	      $ rake build
+
+       You  will  now  have   a   gem	at   private-example/pkg/private-exam-
+       ple-0.1.0.gem.
+
+   1mPushing0m
+       If your Gemstash server isn't running, go ahead and start it:
+
+	      $ gemstash start
+
+       Push your test gem using Rubygems:
+
+	      $ gem push --key test_key --host http://localhost:9292/private pkg/private-example-0.1.0.gem
+
+       The /private portion of the --host option tells Gemstash you are inter-
+       acting  with the private gems.  Gemstash will not let you push, or yank
+       from anything except /private.
+
+   1mBundling0m
+       Once your gem is pushed to your Gemstash server, you are ready to  bun-
+       dle  it.  Create a Gemfile and specify the gem.	You will probably want
+       to wrap the private gem in a source block, and let the rest of Gemstash
+       handle all other gems:
+
+	      # ./Gemfile
+	      source "http://localhost:9292"
+	      gem "rubywarrior"
+
+	      source "http://localhost:9292/private" do
+		gem "private-example"
+	      end
+
+       Notice that the Gemstash server	points	to  /private  again  when  in-
+       stalling  your  private	gem.   Go ahead and bundle to install your new
+       private gem:
+
+	      $ bundle
+
+   1mYanking0m
+       If you push a private gem by  accident,	you  can  yank	the  gem  with
+       Rubygems:
+
+	      $ RUBYGEMS_HOST=http://localhost:9292/private gem yank --key test_key private-example --version 0.1.0
+
+       Like  with  pushing, the /private portion of the host option tells Gem-
+       stash you are interacting with private gems.  Gemstash  will  only  let
+       you  yank  from	/private.   Unlike  pushing,  Rubygems doesn't support
+       --host for yank (yet),  so  you	need  to  specify  the	host  via  the
+       RUBYGEMS_HOST environment variable.
+
+   1mProtected Fetching0m
+       By  default, private gems and specs can be accessed without authentica-
+       tion.
+
+       Private gems often require protected fetching.  For backwards  compati-
+       bility  this  is disabled by default, but can be enabled via $ gemstash
+       setup command.
+
+       When protected fetching is enabled API keys with the permissions all or
+       fetch can be used to download gems and specs.
+
+       On the Bundler side, there are a few ways to configure credentials  for
+       a given gem source:
+
+       Add credentials globally:
+
+	      $ bundle config my-gemstash.dev api_key
+
+       Add credentials in Gemfile:
+
+	      source "https://api_key@my-gemstash.dev"
+
+       However,  it's not a good practice to commit credentials to source con-
+       trol.  A recommended solution is to use	Bundler's  configuration  keys
+       (http://bundler.io/man/bundle-config.1.html#CONFIGURATION-KEYS), e.g.:
+
+	      $ export BUNDLE_MYGEMSTASH__DEV=api_key
+
+       Behind  the  scene,  Bundler  will pick up the ENV var according to the
+       host name (e.g. mygemstash.dev) and add to URI.userinfo for making  re-
+       quests.
+
+       The API key is treated as a HTTP Basic Auth username and any HTTP Basic
+       password supplied will be ignored.
+
+				October 8, 2015       4mgemstash-private-gems24m(7)