Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Roadmap
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
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Admin message
PlayWallDesktop wird heute 10 Jahre alt!
Show more breadcrumbs
Robert Goldmann
Roadmap
Commits
d83fe153
Commit
d83fe153
authored
Sep 23, 2019
by
Robert Goldmann
Browse files
Options
Downloads
Patches
Plain Diff
updated README
parent
703f99db
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+16
-2
16 additions, 2 deletions
README.md
with
16 additions
and
2 deletions
README.md
+
16
−
2
View file @
d83fe153
...
...
@@ -11,10 +11,24 @@ Allows you to create multiple roadmaps for your projects and displays them in a
-
subtasks
-
descriptions for each task and subtask
-
progress bar for upcoming, currently not finished, milestones
-
separated api server and client for rendering the roadmaps
###
[
Inst
ructions](https://github.com/deadlocker8/roadmap/wiki)
### Inst
allation
_Note: needs a MySQL Database_
### #API Server
1.
Set up a fresh PostgreSQL database.
2.
Install the API server pipenv
`pipenv install`
3.
Adjust your settings in
`settings.json`
-
`keyfile`
and
`certfile`
in the section
`server`
must only be filled if
`useSSL`
is set to
`true`
.
-
`secret`
must be filled with a random string to ensure a secure login.
#### Client Server (Renders the roadmaps)
1.
Install the Client pipenv
`pipenv install`
3.
Copy
`settings-example.json`
to
`settings.json`
3.
Adjust your settings in
`settings.json`
-
`keyfile`
and
`certfile`
must only be filled if
`useSSL`
is set to
`true`
.
-
`apiURL`
needs to point ot the url where the API server is running (full url including the port).
-
`secret`
must be filled with a random string to ensure a secure login.
### Screenshots
...
...
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