9bc01ae265
The idea is to filter the sources, replacing @<var>@ occurrences with the mapping for <var> (which is currently hard-coded). @@ -> @. In order to make this work, I had to move the doc sources one directory down (into akka-docs/rst) so that the filtered result could be in a sibling directory so that relative links (to _sphinx plugins or real code) would continue to work. While I was at it I also changed it so that WARNINGs and ERRORs are not swallowed into the debug dump anymore but printed at [warn] level (minimum). One piece of fallout is that the (online) html build is now run after the normal one, not in parallel.
32 lines
920 B
ReStructuredText
32 lines
920 B
ReStructuredText
.. _deployment-scenarios:
|
|
|
|
###################################
|
|
Use-case and Deployment Scenarios
|
|
###################################
|
|
|
|
How can I use and deploy Akka?
|
|
==============================
|
|
|
|
Akka can be used in different ways:
|
|
|
|
- As a library: used as a regular JAR on the classpath and/or in a web app, to
|
|
be put into ``WEB-INF/lib``
|
|
|
|
- As a stand alone application by instantiating ActorSystem in a main class or
|
|
using the :ref:`microkernel-scala` / :ref:`microkernel-java`
|
|
|
|
|
|
Using Akka as library
|
|
---------------------
|
|
|
|
This is most likely what you want if you are building Web applications. There
|
|
are several ways you can use Akka in Library mode by adding more and more
|
|
modules to the stack.
|
|
|
|
|
|
Using Akka as a stand alone microkernel
|
|
----------------------------------------
|
|
|
|
Akka can also be run as a stand-alone microkernel. See
|
|
:ref:`microkernel-scala` / :ref:`microkernel-java` for
|
|
more information.
|