Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Q
quassel-docker
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
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
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
Janne Mareike Koschinski
quassel-docker
Commits
b7b9c988
Verified
Commit
b7b9c988
authored
6 years ago
by
Janne Mareike Koschinski
Browse files
Options
Downloads
Patches
Plain Diff
Updated config path
parent
f436b1a8
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
Dockerfile
+3
-3
3 additions, 3 deletions
Dockerfile
README.md
+5
-5
5 additions, 5 deletions
README.md
with
8 additions
and
8 deletions
Dockerfile
+
3
−
3
View file @
b7b9c988
...
...
@@ -54,9 +54,9 @@ RUN apk add --no-cache \
COPY
--from=builder /quassel/install/bin /usr/bin/
RUN
addgroup
-g
1000
-S
quassel
&&
\
adduser
-S
-G
quassel
-u
1000
-s
/bin/bash
-h
/
quassel
quassel
adduser
-S
-G
quassel
-u
1000
-s
/bin/bash
-h
/
config
quassel
USER
quassel
VOLUME
/
quassel/
VOLUME
/
config
EXPOSE
4242/tcp
EXPOSE
10113/tcp
...
...
@@ -76,4 +76,4 @@ ENV AUTH_LDAP_BASE_DN=""
ENV
AUTH_LDAP_FILTER=""
ENV
AUTH_LDAP_UID_ATTRIBUTE="uid"
ENTRYPOINT
["quasselcore", "--configdir", "/
quassel
", "--config-from-environment"]
ENTRYPOINT
["quasselcore", "--configdir", "/
config
", "--config-from-environment"]
This diff is collapsed.
Click to expand it.
README.md
+
5
−
5
View file @
b7b9c988
...
...
@@ -4,16 +4,16 @@
To use Quassel statefully (which allows you to configure the core on first use)
run it with
`--entrypoint=/usr/bin/quasselcore`
and make sure to include
`--configdir /
quassel
`
as argument.
`--configdir /
config
`
as argument.
If you use the core in this mode, you’ll have to make sure
`/
quassel
`
is stored
If you use the core in this mode, you’ll have to make sure
`/
config
`
is stored
on a volume.
Example usage:
```
bash
docker run
\
-v
/path/to/quassel/volume:/
quassel
\
-v
/path/to/quassel/volume:/
config
\
--entrypoint
=
/usr/bin/quasselcore
\
k8r.eu/justjanne/quassel-docker:v0.13.1
\
--configdir
/quassel
...
...
@@ -40,7 +40,7 @@ Minimal example with SQLite:
```
bash
docker run
\
-v
/path/to/quassel/volume:/
quassel
\
-v
/path/to/quassel/volume:/
config
\
-e
DB_BACKEND
=
SQLite
\
-e
AUTH_AUTHENTICATOR
=
Database
\
k8r.eu/justjanne/quassel-docker:v0.13.1
...
...
@@ -74,7 +74,7 @@ docker run \
You can use the core with SSL, in this case you should either put a
`quasselCert.pem`
file with the full certificate chain and private key into
the
`/
quassel
`
volume, or you can use the
`--ssl-cert`
and
`--ssl-key`
the
`/
config
`
volume, or you can use the
`--ssl-cert`
and
`--ssl-key`
arguments to use separate key and certificate.
## Ports
...
...
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