Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
Deployment
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
freva
Deployment
Commits
f97a89a4
Commit
f97a89a4
authored
3 years ago
by
Martin Bergemann
Browse files
Options
Downloads
Patches
Plain Diff
Update help
parent
db69f440
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+15
-5
15 additions, 5 deletions
README.md
with
15 additions
and
5 deletions
README.md
+
15
−
5
View file @
f97a89a4
...
...
@@ -97,8 +97,7 @@ After successful configuration you can run the ansible deployment. This is done
```
bash
usage: deploy
[
-h
]
[
--config
CONFIG]
[
--steps
{
services,web,backend,db,solr,backup
}
[{
services,web,backend,db,solr,backup
}
...]]
[
--python
PYTHON]
[
--cert
CERT]
[
--backend_arch
{
Linux-aarch64,Linux-ppc64le,Linux-s390x,Linux-x86_64,MacOSX-x86_64
}]
[
--python
PYTHON]
[
--cert
CERT]
[
--wipe
]
[
--ask-pass
]
project_name
Deploy freva.
...
...
@@ -118,15 +117,26 @@ optional arguments:
--cert
CERT,
--cert_file
CERT,
--cert-file
CERT
Path to public certificate file. If none is given, default, a file will be
created.
(
default: None
)
--
backend_arch
{
Linux-aarch64,Linux-ppc64le,Linux-s390x,Linux-x86_64,MacOSX-x86_64
}
,
--backend-arch
{
Linux-aarch64,Linux-ppc64le,Linux-s390x,Linux-x86_64,MacOSX-x86_64
}
Choose the correct deployment architecture
for
the backend.
(
default:
Linux-x86_64
)
--
wipe
This option will empty any pre-existing folders/docker volumes.
(
Useful
for
a
truely fresh start
)
(
default:
False
)
--ask-pass
Connect to server via ssh passwd instead of public key.
(
default: False
)
```
You will need to give a project name, for example
`xces-ces`
or
`regiklim-ces`
.
The
`--steps`
flags can be used if not all services should be deployed.
> **_Note:_** The database name of the the MariaDB database will be set to the project name.
# Accessing the services after deployment:
If the target machine where the services (solr, mariadb, web) where deployed
is a Linux machine you will have a
`systemd`
unit for each service was created.
You can control the the service via systemd. The of the unit has the following
structure
`project_name-service`
. For example
`freva_dev-solr`
:
```
bash
systemctl status freva_dev-solr
```
The same applies for mariadb and web service.
# Kown Issues:
Below are possible solutions to some known issues:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment