9
9
![ Docker Build Status] ( https://github.com/Part-DB/Part-DB-symfony/workflows/Docker%20Image%20Build/badge.svg )
10
10
[ ![ Crowdin] ( https://badges.crowdin.net/e/8325196085d4bee8c04b75f7c915452a/localized.svg )] ( https://part-db.crowdin.com/part-db )
11
11
12
- ** [ Documentation] ( https://docs.part-db.de/ ) ** | ** [ Demo] ( https://part-db.herokuapp.com ) ** | ** [ Docker Image] ( https://hub.docker.com/r/jbtronics/part-db1 ) **
12
+ ** [ Documentation] ( https://docs.part-db.de/ ) ** | ** [ Demo] ( https://demo. part-db.de/ ) ** | ** [ Docker Image] ( https://hub.docker.com/r/jbtronics/part-db1 ) **
13
13
14
14
# Part-DB
15
15
@@ -24,8 +24,8 @@ for everybody.
24
24
25
25
## Demo
26
26
27
- If you want to test Part-DB without installing it, you can use [ this] ( https://part-db.herokuapp.com ) Heroku instance.
28
- (Or this link for the [ German Version] ( https://part-db.herokuapp.com /de/ ) ).
27
+ If you want to test Part-DB without installing it, you can use [ this] ( https://demo. part-db.de/ ) Heroku instance.
28
+ (Or this link for the [ German Version] ( https://demo. part-db.de /de/ ) ).
29
29
30
30
You can log in with username: * user* and password: * user* .
31
31
@@ -101,24 +101,20 @@ for a detailed guide how to install Part-DB.**
101
101
In bigger instances with concurrent accesses, MySQL is more performant. This can not be changed easily later, so
102
102
choose wisely.
103
103
4 . Install composer dependencies and generate autoload files: ` composer install -o --no-dev `
104
- 5 . If you have put Part-DB into a subdirectory on your server (like ` part-db/ ` ), you have to edit the file
105
- ` webpack.config.js ` and uncomment the lines (remove the ` // ` before the lines) ` .setPublicPath('/part-db/build') ` (
106
- line 43) and
107
- ` .setManifestKeyPrefix('build/') ` (line 44). You have to replace ` /part-db ` with your own path on line 44.
108
- 6 . Install client side dependencies and build it: ` yarn install ` and ` yarn build `
109
- 7 . _ Optional_ (speeds up first load): Warmup cache: ` php bin/console cache:warmup `
110
- 8 . Upgrade database to new scheme (or create it, when it was empty): ` php bin/console doctrine:migrations:migrate ` and
104
+ 5 . Install client side dependencies and build it: ` yarn install ` and ` yarn build `
105
+ 6 . _ Optional_ (speeds up first load): Warmup cache: ` php bin/console cache:warmup `
106
+ 7 . Upgrade database to new scheme (or create it, when it was empty): ` php bin/console doctrine:migrations:migrate ` and
111
107
follow the instructions given. During the process the password for the admin is user is shown. Copy it. ** Caution** :
112
108
This steps tamper with your database and could potentially destroy it. So make sure to make a backup of your
113
109
database.
114
- 9 . You can configure Part-DB via ` config/parameters.yaml ` . You should check if settings match your expectations, after
110
+ 8 . You can configure Part-DB via ` config/parameters.yaml ` . You should check if settings match your expectations, after
115
111
you installed/upgraded Part-DB. Check if ` partdb.default_currency ` matches your mainly used currency (this can not be
116
112
changed after creating price information).
117
113
Run ` php bin/console cache:clear ` when you changed something.
118
- 10 . Access Part-DB in your browser (under the URL you put it) and login with user * admin* . Password is the one outputted
119
- during DB setup.
120
- If you can not remember the password, set a new one with ` php bin/console app:set-password admin ` . You can create
121
- new users with the admin user and start using Part-DB.
114
+ 9 . Access Part-DB in your browser (under the URL you put it) and login with user * admin* . Password is the one outputted
115
+ during DB setup.
116
+ If you can not remember the password, set a new one with ` php bin/console app:set-password admin ` . You can create
117
+ new users with the admin user and start using Part-DB.
122
118
123
119
When you want to upgrade to a newer version, then just copy the new files into the folder
124
120
and repeat the steps 4. to 7.
0 commit comments