You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Get UserFrosting repository : `docker run --rm -it -v "$(pwd):/app" composer create-project userfrosting/userfrosting UserFrosting "^5.0" --no-scripts --no-install --ignore-platform-reqs`
10
-
2. Change to the new directory `cd UserFrosting`
11
-
3. Run `docker-compose build --no-cache` to build all the docker containers.
12
-
4. Run `docker-compose up -d` to to start all the containers.
13
-
5. Run `sudo chown -R $USER: .` and `sudo chmod 777 app/{logs,cache,sessions}` to set some directory permissions (your may have to enter your root password):
14
-
6. Run `docker-compose exec app composer update` to install all composer modules used in UserFrosting.
15
-
7. Run `docker-compose exec app php bakery bake` to install UserFrosting (database configuration and migrations, creation of admin user, ...). You'll need to provide info to create the admin user.
If you need to stop the UserFrosting docker containers, just change to your userfrosting directory and run:
37
64
38
-
`docker-compose stop`
65
+
```
66
+
docker-compose stop
67
+
```
39
68
40
69
To start containers again, change to your userfrosting directory and run:
41
70
42
-
`docker-compose up -d`
71
+
```
72
+
docker-compose up -d
73
+
```
43
74
44
75
**Purge docker containers to start over**
45
76
@@ -55,8 +86,7 @@ And then start the installation process again.
55
86
56
87
You may be tempted to run with this in production but this setup has not been security-hardened. For example:
57
88
58
-
- Database is exposed on port 8593 so you can access MySQL using your favorite client at localhost:8593. However,
59
-
the way Docker exposes this actually bypasses common firewalls like `ufw` so this should not be exposed in production.
89
+
- Database is exposed on port 8593 so you can access MySQL using your favorite client at localhost:8593. However, the way Docker exposes this actually bypasses common firewalls like `ufw` so this should not be exposed in production.
60
90
- Database credentials are hard-coded so obviously not secure.
61
91
- File permissions may be more open than necessary.
0 commit comments